diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/MESHBAY_DESIGN.md | 9 | ||||
| -rw-r--r-- | docs/USERGUIDE.md | 14 |
2 files changed, 14 insertions, 9 deletions
diff --git a/docs/MESHBAY_DESIGN.md b/docs/MESHBAY_DESIGN.md index 49baa6a..a9502d8 100644 --- a/docs/MESHBAY_DESIGN.md +++ b/docs/MESHBAY_DESIGN.md @@ -702,8 +702,9 @@ groups, and it is made **in the desktop application, never in a browser**: The hub keeps a **mirror** of the setting as a preference (`browser_access`), written by the application at each start and change. It grants nothing — no node reads it — and exists so a browser can say why a group will not open and name the -way in: turn it on from the application, or approve this browser from it (device -linking, §3.3), which gives the browser identities of its own. Were a browser able +way in: turn it on from the application. A browser is not linked as a device (§3.3): +it keeps no identity between connections, so a key approved for it would be gone by +the next one. Were a browser able to turn it on, somebody holding only the passphrase could sign in on the web, flip it, and have the owner's own application upload the identities at its next start — under the pepper that same sign-in hands out. @@ -1116,8 +1117,8 @@ the proof, because each is something a caller needs *in order to* prove possessi of the group key: a returning browser has to recover its identity, a new member has no key to prove with, and a new device of a known member has none either — the group key is wrapped for an identity the node pinned, and a machine that keeps no -bundle there (the desktop application, the command-line client, a browser with -browser access off) holds no such identity until another device approves it. +bundle there (the desktop application, the command-line client) holds no such +identity until another device approves it. Nothing else qualifies. Filing a device request is **inert**: nothing is admitted until a device already pinned countersigns it, the code is bound to the new keys, the request is bounded per connection (5) and per account (10 pending), and it is diff --git a/docs/USERGUIDE.md b/docs/USERGUIDE.md index 1c21c80..09d264e 100644 --- a/docs/USERGUIDE.md +++ b/docs/USERGUIDE.md @@ -212,10 +212,14 @@ a browser can open your groups with your passphrase. With it off — the default an account created in the application — your keys stay on this computer and nothing of them is left on anybody's node. With it on, the application leaves a locked copy on each node, as a browser would. The change reaches each group the -next time it opens. A browser can also be approved from the application for -itself, group by group: the browser shows a linking code (*Get a linking code*), -and you enter it in the application under *Your devices on this node*. That gives -the browser keys of its own without turning browser access on. +next time it opens. With it off, only the application (and the command-line +client) opens your groups: a browser keeps no keys between visits, so it cannot be +linked as a device of its own. + +On another computer, the application opens a group with keys of its own once a +device already linked approves it: the group shows a linking code (*Get a linking +code*), you enter it on that device under *Your devices on this node*, and the +group opens by itself. The application asks in a small window of its own, not in the page, before it hosts a group on this computer, shares a folder you did not pick in its folder @@ -1071,7 +1075,7 @@ fresh invitation code. **"Browser access is off for this account."** The account keeps its keys in the desktop application. Turn browser access on -there (Profile), or approve this browser from it. +there (Profile). **Video says the codec is not supported.** The source codec has no decoder in that browser and transcoding is off, or |