Commit Graph

127 Commits

Author SHA1 Message Date
0485eeb126 Attempt to explain inclusion of lease secrets in the body 2021-03-30 10:03:03 -04:00
6520d3a505 add the APIs 2021-03-22 13:44:48 -04:00
4a117e5d9b Also get rid of the footnote target 2021-03-22 09:25:22 -04:00
bc86820273 Change v=2 to v=1 2021-03-22 09:10:35 -04:00
0d2e9e8e6a match local prevailing convention for naming 2021-03-19 15:43:40 -04:00
6aad53a598 explain why this conclusion is fine 2021-03-19 15:03:36 -04:00
e3a6d75962
Remove the obvious documentation references 2020-02-13 10:23:27 -05:00
d964be6340 remove code details 2019-06-23 11:12:55 -06:00
33090ef6e2 remove last remaining references to pycryptopp 2019-06-13 22:19:28 -06:00
687c4c8f4f Talk about lack of creation 2018-06-29 11:30:45 -04:00
635c0c5db0 Slots are not separately, explicitly created 2018-06-29 11:30:28 -04:00
250465f810 Discard base32 and SHA1. 2018-06-29 11:11:30 -04:00
ff12263ed5 remove an extra extra word 2018-06-27 16:53:37 -04:00
209c8694f9 Simplify language 2018-06-27 16:53:17 -04:00
4cd018fc11 Consistently name the gbs information
And replace the flag with the full information otherwise the client
cannot find the gbs server without talking to the introducer again.
2018-06-27 16:51:47 -04:00
4e5ec27d50 Use that : notation consistently here 2018-06-27 16:49:45 -04:00
145ee3b6ab mention the introducer 2018-06-27 16:39:02 -04:00
c43eacc3a9 clarify which party is vulnerable 2018-06-13 08:27:45 -04:00
c3011a434b Specify preferred encoding and encoding negotiation 2018-06-06 13:46:45 -04:00
b8cfee79e3 frame it a little more 2018-06-06 13:31:34 -04:00
4e10f7971a discuss decision to use query args 2018-05-29 10:52:37 -04:00
3d3c3d2eb4 elaborate on the transition stages
talk about cases of each stage and desired behavior
2018-05-22 09:57:39 -04:00
a592053b18 refer to GBS more than HTTP 2018-05-22 09:57:29 -04:00
534b8db318 markup and spelling 2018-05-22 09:57:18 -04:00
acf541a0be try to make the example more useful 2018-05-22 09:08:59 -04:00
504452f1fd clean up description of certificate validity period 2018-05-22 09:00:30 -04:00
ab37b5eabb clean up the description of the tls usage 2018-05-22 09:00:10 -04:00
65103445ea secrecy is the kind of security we're talking about here 2018-05-22 08:43:19 -04:00
97176e88d4 but it is part of this proposed solution 2018-05-22 08:43:12 -04:00
bf305b91e4 HTTP *per se* is not a requirement 2018-05-22 08:42:55 -04:00
5ede9662bb fix typo 2018-05-22 08:42:39 -04:00
44afc1de03 talk about a non-security requirement! 2018-05-22 08:42:28 -04:00
ff48e67418 flop some heading levels around 2018-05-22 08:42:16 -04:00
c321c937f6 copy edits and another option for tubID length 2018-05-22 08:27:31 -04:00
b73e95ec30 discuss protocol identification 2018-05-22 08:27:24 -04:00
17ae8a191b I like it 2018-05-22 08:27:15 -04:00
4592bf3de2 wip - more edits of the security material & transition plan 2018-05-21 16:23:53 -04:00
176732dcaf gotta announce the new fURL sometime 2018-05-21 14:59:46 -04:00
16076f9bd7 be explicit about the security goals being achieved 2018-05-21 14:59:28 -04:00
11184939e8 It's SPKI not public key 2018-05-21 14:59:10 -04:00
fa4384e36e add a security summary (noting foolscap features)
also, expanded discussion.
2018-05-21 14:14:53 -04:00
cea0ae8004 tahoe-lafs is already good at redundant storage 2018-05-21 14:14:39 -04:00
4626a09224 elaborate on reputation-based assumptions 2018-05-21 13:31:16 -04:00
931ffec005 semantic newlines 2018-05-21 13:31:10 -04:00
d09b613d59 make mutable and immutable read the same 2018-05-18 15:45:22 -04:00
f4b59b166d no more int-key mappings 2018-05-18 13:08:13 -04:00
3898911fcc consistent title levels 2018-05-18 13:07:18 -04:00
f09ed91ab6 collapse these two APIs, they are the same
also add mutable .../shares listing
2018-05-18 13:01:57 -04:00
9388903515 need a way to advise of corrupt mutable shares 2018-05-18 13:01:45 -04:00
c6a8e4535c mount this beneath the storage index resource 2018-05-18 13:01:19 -04:00