You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/security/MANIFEST_SIGNING.md
+15-2Lines changed: 15 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -186,6 +186,17 @@ The signature blob encoding follows the minisign specification. For reference, t
186
186
187
187
**Note**: Applications should use the verification module (`manifest-signature.js`) rather than parsing the signature format directly. The exact wire format is defined by the minisign specification and may vary in optional fields.
188
188
189
+
## CLI Verification Modes
190
+
191
+
The `aiox validate` command uses a compatibility-safe default:
192
+
193
+
- If `.aiox-core/install-manifest.yaml.minisig` exists in the target or repair source, the signature is verified automatically.
194
+
- If no `.minisig` was distributed with the package, validation continues without signature verification and still verifies file hashes.
195
+
- Strict enforcement is available with `aiox validate --require-signature` or `AIOX_REQUIRE_SIGNATURE=1`.
196
+
- Emergency recovery can explicitly bypass verification with `aiox validate --no-signature`.
197
+
198
+
This keeps unsigned public packages installable while preserving an explicit strict mode for signed releases and controlled environments.
199
+
189
200
## Development Mode
190
201
191
202
During development and testing, signature verification can be bypassed:
This option exists **exclusively** for local development environments. Production builds **MUST** enforce signature verification (`requireSignature: true`). Any deployment with signature verification disabled should be considered insecure.
217
+
This option exists **exclusively** for local development, recovery, and unsigned package compatibility. Production builds that distribute `.minisig` artifacts **MUST** enforce signature verification (`requireSignature: true`) or run `aiox validate --require-signature`. Any deployment with signature verification disabled should be considered unsigned.
@@ -281,7 +294,7 @@ Loads and verifies a manifest file.
281
294
**Parameters:**
282
295
283
296
-`manifestPath` (string): Path to manifest file
284
-
-`options.requireSignature` (boolean): Fail if signature missing (default: true)
297
+
-`options.requireSignature` (boolean): Fail if signature missing (default: true for the library API; CLI default is resolved by `.minisig` presence or strict flags)
0 commit comments