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
fb9317ed80
change versions in INSTALL
2018-05-18 14:41:48 -06:00
9bc8b69663
a couple additions to CREDITS
2018-05-18 14:41:48 -06:00
123bffb18b
update NEWS for new release
2018-05-18 14:41:48 -06:00
ae2f6f6ef2
script to fetch PR information from GitHub
2018-05-18 14:41:34 -06:00
43c0c0b3ec
start doc changes for new release
2018-05-18 14:32:30 -06: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
69195e0a5a
maybe we don't even want Range
2018-05-18 13:01:10 -04:00
6c664d69a8
consistent non-abbreviation
2018-05-18 13:01:03 -04:00
9402698918
Harmonize hyphens
2018-05-18 11:11:04 -04:00
943b389d77
Banish slots and deemphasize buckets
2018-05-18 11:09:17 -04:00
3ef1ceeead
markup
2018-05-18 09:13:57 -04:00
dd78fe81d0
note the failure case
2018-05-18 09:05:46 -04:00
fb51c1df40
correct the sample code
2018-05-18 09:05:37 -04:00
00ae3b5663
discuss encoded hash length
2018-05-18 09:05:25 -04:00
d3f9ee2406
link to a different upload resume strategy
2018-05-17 15:09:50 -04:00
113af95984
when you are sending a range, you use Content-Range
...
when you are _asking_ for a range, you use Range
2018-05-17 15:08:03 -04:00
2bbe51a01d
Discuss Range requests for uploads
2018-05-17 14:11:37 -04:00
d011c2f936
rst twiddles
2018-05-17 14:11:32 -04:00
eb9b44885e
simple naming mistake
...
this must be a different endpoint or it is ambiguous with bucket
interactions. plus it makes more sense that "place where storage
indexes are" is different from "place where buckets are" although I
am still uncomfortable with the idea that "storage indexes" are things
and not ... indexes ...
2018-05-17 14:01:46 -04:00
4e99f22c2b
make containers plural I suppose
2018-05-17 14:01:36 -04:00
1d3f9715f8
trivial json markup fix
2018-05-17 14:01:18 -04:00
5fa71484e3
call out the base32/base64 mismatch
2018-05-16 10:16:58 -04:00
67ff44039f
add values to the example
2018-05-16 09:49:58 -04:00
4bed6363a3
be specific about public key comparison
2018-05-16 09:49:48 -04:00
Jean-Paul Calderone
91c655298a
Merge pull request #494 from meejah/2909.reliable-test.0
...
Fix Magic Folder integration test.
Previously it waited for 2 conflicting files but there's no guarantee both sides will conflict in this scenario. The test should be satisfied with at least one side conflicting (and the assertions it makes already are).
2018-05-16 07:56:56 -04:00
4ad5b5ab46
address slots
2018-05-15 16:00:40 -04:00
