aboutsummaryrefslogtreecommitdiffstats
path: root/docs
Commit message (Expand)AuthorAgeFilesLines
* state: limit refused writes per usertv5 days2-1/+9
* roots: an epoch's root pinned, and named in every handshaketv5 days4-1/+21
* screen: what a node receives judged, policy or nottv5 days1-5/+6
* store: a write inside a list checked where the rules judge ittv5 days1-1/+3
* bench: what screening costs while catching uptv5 days1-2/+2
* strict: no strict remake of a swarm strict alreadytv5 days1-1/+3
* refusals: a big drop waits for a second member only where there is onetv5 days1-4/+6
* remake: aborts written as the user who asks; no abort by timetv5 days2-8/+8
* strict: a manifest serves one remake, at its basetv5 days1-1/+2
* docs: what a junk logout doestv5 days1-1/+5
* remake: no --follow-strict-remakes; a strict remake failing says whotv5 days2-11/+8
* remake: turning a running swarm strict, keeping what an operator signedtv5 days4-4/+82
* dashboard: a user's menu, with its credentials and logging outtv5 days1-3/+6
* users: a user can't remove its own last keytv5 days1-1/+2
* auth: no basic authentication offered to the dashboardtv5 days1-1/+2
* refusals: a drop taking much waits for a second member, and showstv5 days2-1/+6
* users: a user manages its own keystv5 days2-1/+49
* login: logins by key capped per usertv5 days2-3/+15
* dashboard: log out of this browser, and say what can't betv5 days2-2/+6
* docs: a signed null keeps the prev chain goingtv5 days1-1/+4
* docs: what the review found that staystv5 days2-5/+22
* login: the session cookie Secure behind a TLS proxytv5 days1-1/+4
* dashboard: a content security policy, framed by nonetv5 days1-1/+2
* envelope: a signed value names its swarmtv5 days3-7/+10
* token: a banned node's tokens aren't takentv5 days1-3/+3
* dashboard: hand over a token reading the member list onlytv5 days2-5/+6
* login: a token asked to live less ends its session with ittv5 days2-3/+4
* rules: an expired remake aborted by any membertv5 days2-2/+8
* docs: a member's entry, as the rules have ittv5 days1-3/+4
* rules: a carried remake record taken from the coordinator its snapshot namestv5 days1-1/+2
* rules: protocol maps judged by what is done to themtv5 days1-2/+7
* screen: a signature vouches for its change and what it builds ontv5 days2-4/+8
* sync: a member refused as a whole, synced with again once it changed documenttv5 days1-2/+3
* remake: replays judged before they go intv5 days1-0/+4
* access: a node judges its own changes before they leavetv5 days1-0/+6
* remake: replay from the quarantine where the user may writetv5 days2-4/+16
* access: forgetting and revoking as the API letstv5 days1-2/+3
* access: maps made on the way judged by what they holdtv5 days1-0/+2
* access: judged by the policy written undertv5 days1-1/+3
* access: a forgotten node cancels its own recordtv5 days1-0/+1
* dashboard: message flashestv5 days1-2/+6
* dashboard: a token handed over to another member's dashboardtv5 days3-3/+10
* swarm: changes taken unjudged, dropped (REFUSALS)tv5 days4-4/+18
* access: members refused as a wholetv5 days4-3/+22
* auth: the session cookie lets in reads onlytv5 days2-2/+6
* access: refused oncetv5 days1-1/+4
* docs: trust as it standstv5 days1-32/+60
* auth: a login page and browser sessionstv5 days3-2/+66
* docs: reading keys and declarationstv5 days1-0/+18
* scripts: sealing and opening in the reference clienttv5 days1-0/+4