Minor fixes

This commit is contained in:
artur 2024-10-29 16:44:54 +01:00
parent c23ec0672c
commit 0a2eb9df5c

4
146.md
View File

@ -60,7 +60,7 @@ If client receives `errorNoKey:<requestEvent.id>` reply matching one of pending
When user clicks on `Continue` button in rebinder iframe, it MUST open a top-level signer popup. The popup MUST check that provided `local_pubkey` has permissions to access `remote_user_pubkey` and then MUST pass the user private key to rebinder iframe. Details are implementation-defined, see appendix for recommendations. When user clicks on `Continue` button in rebinder iframe, it MUST open a top-level signer popup. The popup MUST check that provided `local_pubkey` has permissions to access `remote_user_pubkey` and then MUST pass the user private key to rebinder iframe. Details are implementation-defined, see appendix for recommendations.
After rebinder iframe has finished importing the user private key, it MUST notify the client by calling `window.parent.postMessage("rebinderDone", "*")`. When client receives the `rebinerDone` from iframe_url's origin it MAY destroy the rebinder iframe. After rebinder iframe has finished importing the user private key, it MUST notify the client by calling `window.parent.postMessage("rebinderDone", "*")`. When client receives the `rebinderDone` from iframe_url's origin it MAY destroy the rebinder iframe.
When worker iframe that has paused the request notices that user private key was imported by rebinder into the local store, it MUST restart the paused call and deliver the reply to the client. When worker iframe that has paused the request notices that user private key was imported by rebinder into the local store, it MUST restart the paused call and deliver the reply to the client.
@ -74,6 +74,6 @@ When worker iframe that has paused the request notices that user private key was
- Starter iframe SHOULD check that `auth_url` has valid origin. - Starter iframe SHOULD check that `auth_url` has valid origin.
- Starter/rebinder MAY use `MessageChannel` to create a port that will be transferred to top-level signer and to it's service-worker so that it could then export the user private key to the iframe signer. - Starter/rebinder MAY use `MessageChannel` to create a port that will be transferred to top-level signer and to it's service-worker so that it could then export the user private key to the iframe signer.
- Client MAY save the `iframe_url` to local storage and reuse it until logout. - Client MAY save the `iframe_url` to local storage and reuse it until logout.
- Client MAY send normal nip-46 requests over relay in paralles to iframe requests, in which case it SHOULD deduplicate the replies across both channels. - Client MAY send normal nip-46 requests over relay in parallel to iframe requests, in which case it SHOULD deduplicate the replies across both channels.
- Signer SHOULD use random auxiliary sub-domains to serve `iframe_url` - Chrome desktop allows users to delete signer's storage on client's tab, which (mistakenly?) removes top-level signer storage too and users' keys might be lost. - Signer SHOULD use random auxiliary sub-domains to serve `iframe_url` - Chrome desktop allows users to delete signer's storage on client's tab, which (mistakenly?) removes top-level signer storage too and users' keys might be lost.
- Top-level signer MAY export `local client pubkey` to iframe along with user private key to scope the iframe signer to this particular connection. - Top-level signer MAY export `local client pubkey` to iframe along with user private key to scope the iframe signer to this particular connection.