warpmetal 0.2.2 → 0.2.3
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
|
@@ -65,6 +65,9 @@ alternate state directory.
|
|
|
65
65
|
permissions where the platform supports POSIX modes.
|
|
66
66
|
- The CLI passes an SSH private-key path directly to `ssh-keygen`; it never
|
|
67
67
|
reads the private key.
|
|
68
|
+
- WarpMetal applies key-only OpenSSH configuration on initial provisioning and
|
|
69
|
+
every OS reload. Password and keyboard-interactive login are disabled; never
|
|
70
|
+
request, store, or expect a VPS login password.
|
|
68
71
|
- The CLI accepts an externally produced x402 `PAYMENT-SIGNATURE` from a file.
|
|
69
72
|
Wallet key management and signing remain outside this package.
|
|
70
73
|
- Destructive or state-changing commands require explicit confirmations and
|
package/package.json
CHANGED
|
@@ -26,6 +26,11 @@ Never read, print, summarize, upload, or commit the WarpMetal state file. Never
|
|
|
26
26
|
read an SSH private-key file. Pass its path only to a command designed to use
|
|
27
27
|
it. Never request or handle a wallet seed phrase or private key.
|
|
28
28
|
|
|
29
|
+
WarpMetal provisions and reloads servers with key-only OpenSSH access. Password
|
|
30
|
+
and keyboard-interactive login are disabled, including for root. Never request,
|
|
31
|
+
store, invent, or expect a VPS login password; use the submitted public key and
|
|
32
|
+
its matching private-key path.
|
|
33
|
+
|
|
29
34
|
## Discover before acting
|
|
30
35
|
|
|
31
36
|
Run:
|
|
@@ -88,6 +93,11 @@ Poll a prepared or paid order with:
|
|
|
88
93
|
warpmetal order status --task <taskId> --wait --json
|
|
89
94
|
```
|
|
90
95
|
|
|
96
|
+
After initial provisioning and every OS reload, WarpMetal reapplies the same
|
|
97
|
+
key-only policy: `PasswordAuthentication no`,
|
|
98
|
+
`KbdInteractiveAuthentication no`, `PermitRootLogin prohibit-password`, and
|
|
99
|
+
`AuthenticationMethods publickey`.
|
|
100
|
+
|
|
91
101
|
For routine management, prove possession of the installed SSH key without
|
|
92
102
|
reading it:
|
|
93
103
|
|
|
@@ -25,6 +25,10 @@
|
|
|
25
25
|
- Never read or transmit an SSH private key. Pass only its filesystem path to
|
|
26
26
|
`warpmetal server login`, `warpmetal runtime install`,
|
|
27
27
|
`warpmetal sandbox connect`, or `ssh-keygen`.
|
|
28
|
+
- WarpMetal disables VPS password and keyboard-interactive SSH login after
|
|
29
|
+
initial provisioning and every OS reload. Never request, store, invent, or
|
|
30
|
+
expect a VPS login password; use the submitted public key and matching
|
|
31
|
+
private-key path.
|
|
28
32
|
- Never place the owner SSH key, owner token, management access token, runtime
|
|
29
33
|
bootstrap, supervisor node token, or state file inside a sandbox.
|
|
30
34
|
- Give each agent a distinct sandbox-specific SSH key and grant. Never reuse
|