warpmetal 0.8.1 → 0.8.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -98,6 +98,11 @@ checkout returns `serverId`, the CLI binds that ID to the identity so
98
98
  an `--identity` flag. Use `--ssh-public-key-file` instead when supplying a
99
99
  user-managed public key.
100
100
 
101
+ WarpMetal installs the owner key for `root` on every supported image. The SSH
102
+ key does not encode a login username: use `root@<server-ip>` for an owner shell
103
+ and `--ssh-user root` for runtime installation, not a distribution convention
104
+ such as `ubuntu`.
105
+
101
106
  Pass `--json` for structured, secret-redacted output. Use
102
107
  `WARPMETAL_API_URL` for an alternate API origin and `WARPMETAL_HOME` for an
103
108
  alternate state directory.
@@ -304,7 +309,7 @@ compatible external signer.
304
309
  warpmetal runtime enable --server <serverId> --json
305
310
  warpmetal runtime install \
306
311
  --server <serverId> \
307
- --ssh-user ubuntu \
312
+ --ssh-user root \
308
313
  --confirm INSTALL \
309
314
  --wait \
310
315
  --json
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "warpmetal",
3
- "version": "0.8.1",
3
+ "version": "0.8.2",
4
4
  "description": "Agent-safe CLI and skill for purchasing, renewing, and managing WarpMetal VPS servers",
5
5
  "type": "module",
6
6
  "bin": {
@@ -209,6 +209,13 @@ key-only policy: `PasswordAuthentication no`,
209
209
  `KbdInteractiveAuthentication no`, `PermitRootLogin prohibit-password`, and
210
210
  `AuthenticationMethods publickey`.
211
211
 
212
+ The WarpMetal owner SSH account is `root` on every supported image. SSH public
213
+ keys do not bind a login username. Use `root@<server-ip>` for an owner shell and
214
+ pass `--ssh-user root` whenever a CLI command asks for the owner SSH account;
215
+ never infer `ubuntu` or another distribution-default username. This does not
216
+ apply to `sandbox connect`, which uses the gateway username from its connection
217
+ profile.
218
+
212
219
  For routine management, prove possession of the installed SSH key without
213
220
  reading it:
214
221
 
@@ -202,7 +202,7 @@ process listings.
202
202
  warpmetal runtime enable --server <serverId> [--idempotency-key <key>] --json
203
203
  warpmetal runtime get --server <serverId> [--wait] [--timeout-seconds <n>] --json
204
204
  warpmetal runtime install \
205
- --server <serverId> [--identity <owner-key>] --ssh-user <admin-user> \
205
+ --server <serverId> [--identity <owner-key>] --ssh-user root \
206
206
  --confirm INSTALL [--wait] [--timeout-seconds <n>] --json
207
207
 
208
208
  warpmetal sandbox create \
@@ -48,12 +48,15 @@ the existing separate interactive-or-autonomous payment authority check.
48
48
 
49
49
  For an existing ready server:
50
50
 
51
+ Use the WarpMetal owner account `root` for every supported host image; do not
52
+ substitute a distribution-default account such as `ubuntu`.
53
+
51
54
  ```sh
52
55
  warpmetal runtime enable --server <serverId> --json
53
56
  warpmetal runtime install \
54
57
  --server <serverId> \
55
58
  --identity <owner-private-key-path> \
56
- --ssh-user <os-admin-user> \
59
+ --ssh-user root \
57
60
  --confirm INSTALL \
58
61
  --wait \
59
62
  --json