@kehto/paja 0.24.5 → 0.25.1
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 +26 -15
- package/dist/browser-host.js +497 -114
- package/dist/browser-host.js.map +1 -1
- package/dist/{chunk-PLZYKUBM.js → chunk-FGY4IESF.js} +14 -8
- package/dist/chunk-FGY4IESF.js.map +1 -0
- package/dist/cli.js +1 -1
- package/dist/index.js +1 -1
- package/package.json +3 -3
- package/dist/chunk-PLZYKUBM.js.map +0 -1
package/README.md
CHANGED
|
@@ -81,21 +81,32 @@ available, can connect to a bunker/NIP-46 URI, and only uses the generated local
|
|
|
81
81
|
development signer when the Dev signer button is selected. Sign, publish, DM
|
|
82
82
|
send, filesystem picker, Blossom upload, and external-link requests use one serialized in-page
|
|
83
83
|
confirmation dialog. Deny has initial focus and Escape denies. A napplet-scoped
|
|
84
|
-
sign request defaults to one-time approval
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
|
|
84
|
+
sign or publish request defaults to one-time approval. The modal can remember
|
|
85
|
+
one event kind, all events for the current action, or **all signing and publishing
|
|
86
|
+
from this napplet version**. Signing-only permission never implies publication;
|
|
87
|
+
the combined choice explicitly grants both. The dialog shows the napplet,
|
|
88
|
+
artifact/version, source scope and signer, with a warning about future effects.
|
|
89
|
+
Grants bind the active account to the host's verified manifest identity (including
|
|
90
|
+
publisher) and artifact hash. Signed versions can reuse approval after reload;
|
|
91
|
+
another manifest, version or account asks again. Local single-file targets use
|
|
92
|
+
their content hash in a separate local scope. Direct development URLs are mutable,
|
|
93
|
+
so approvals last only for the current document/frame load and must be renewed
|
|
94
|
+
after reload; HMR can still change that development session's running code.
|
|
95
|
+
CVM without a user signer uses a separate, document-scoped host-generated
|
|
96
|
+
principal; its approvals never transfer to a user account or another host session.
|
|
97
|
+
Otherwise, unknown identity/account/kind remains one-shot. Denials are never remembered.
|
|
98
|
+
Signer controls revoke every remembered signing/publication approval; failed
|
|
99
|
+
durable deletion is reported instead of claiming revocation. Missing browser
|
|
100
|
+
storage makes new choices memory-only. An ephemeral Dev account changes on a
|
|
101
|
+
full host reload and therefore asks again. Older signing-only records are retained
|
|
102
|
+
without gaining publication and emit `KEHTO-PAJA-SIGNER-CONSENT-V1` once per host
|
|
103
|
+
module lifetime; current records stay quiet. Removing a window or changing the
|
|
104
|
+
signer denies pending signing/publication. Link requests always use the modal,
|
|
105
|
+
and the external browser handoff runs directly from its approval click with
|
|
106
|
+
`noopener,noreferrer`. Other operation permissions remain separate.
|
|
107
|
+
This is Paja host policy under [NAP-RELAY PR #2 at `9f30b350`](https://github.com/napplet/naps/blob/9f30b3505335a52c574ff570576687d6467021ff/naps/NAP-RELAY.md),
|
|
108
|
+
[NAP-OUTBOX PR #32 at `8865f73d`](https://github.com/napplet/naps/blob/8865f73d52a4864afee145f28d26520476273927/naps/NAP-OUTBOX.md)
|
|
109
|
+
and [NAP-LINK PR #53 at `50a2cd45`](https://github.com/napplet/naps/blob/50a2cd45e76f06e87b87e93842badf4c61f17bde/naps/NAP-LINK.md), rather than
|
|
99
110
|
a Kehto kernel default. Upload consent identifies the requesting napplet, file, MIME type,
|
|
100
111
|
size, selected server, and durable public effect before bytes leave the browser.
|
|
101
112
|
A denial or a live publish with no accepting relay returns a canonical failure
|