fbd2374ef0
point to the new doc site
2018-07-03 13:03:48 -04:00
e1c1cd1637
Verisimilitude
2018-07-03 13:03:23 -04:00
8401201868
convey the basis for our prediction
...
instead of the prediction.
we know the basis is true.
who knows about the prediction.
2018-07-03 13:02:41 -04:00
e2ceb4f8e4
Spelling fix
2018-07-02 15:38:10 -04:00
de95a2092a
Refer to wallet documentation
2018-07-02 15:34:35 -04:00
fad4ffe37e
Point to the new doc from existing config docs
...
Perhaps this will make it more likely folks will find the information.
2018-07-02 15:29:51 -04:00
df7de6cb90
Document a convention for encouraging donations
...
The convention smuggles an address in the node nickname and uses Zcash
shielded transactions for privacy.
2018-07-02 15:24:10 -04:00
Jean-Paul Calderone
c48fec5b03
Merge pull request #499 from LeastAuthority/2925.http-storage-node-protocol-spec
...
Add an initial "Great Black Swamp" protocol specification proposal.
Fixes ticket:2925
2018-06-29 13:13:37 -04: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
fb9317ed80
change versions in INSTALL
2018-05-18 14:41:48 -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
4ad5b5ab46
address slots
2018-05-15 16:00:40 -04:00
c824bcd8b2
make the share a logical child of the bucket?
2018-05-15 15:28:03 -04:00
6d84cd8179
these are gone
2018-05-15 15:27:53 -04:00
178cb58a57
dunno how much the risk is elevated
2018-05-15 15:27:33 -04:00
6b72750397
reduce verticality
2018-05-15 15:27:26 -04:00
5f88cd0687
rework the security section
2018-05-15 15:16:01 -04:00
357820357c
front matter
2018-05-15 15:04:20 -04:00
465489fd0b
re-organize
2018-05-15 14:48:42 -04:00
23242266dc
consistent style
2018-05-15 14:16:02 -04:00
a3d4edca7d
retrieve server version and info
2018-05-15 10:10:21 -04:00
73d903ad96
client-selected resource identifier -> PUT
2018-05-15 09:42:20 -04:00
5b35f591f1
write share data
2018-05-15 09:42:10 -04:00
b6572e2856
clear now they are not necessarily consecutive
2018-05-15 09:41:45 -04:00
599bf074e3
more spurious indentation
2018-05-15 09:07:58 -04:00
8e9ba52118
spurious indentation
2018-05-15 09:07:07 -04:00
53dce7eafc
first pass over read and write api
2018-05-14 15:58:21 -04:00
c612fb7075
initial pass over security section
2018-05-14 14:30:34 -04:00
b9939f7d4d
link to inotify wikipedia page
2018-04-20 14:42:33 -04:00
6fd1f12a3c
doc improvements related to the storage dir
2018-03-19 15:28:44 -04:00
Ruben Pollan
136de7d7f7
Add storage_dir config field
...
On the [storage] section of the tahoe.cfg now there is a field
'storage_dir' where the path to the storage folder can be configured.
2018-03-19 11:20:04 -04:00
0b25cad71e
documentation fixups from daira's review
2018-02-06 15:28:02 -07:00
1171bf13af
ticket #2882 : preserve user mtime
2018-02-06 15:27:56 -07:00
tpltnt
c3a91376f3
added link to RFC 822
2018-01-06 15:12:16 +01:00
tpltnt
a6655040b2
added link tp ConfigParser documentation
2018-01-06 15:10:30 +01:00
tpltnt
1896335eda
added link to wikipedia article on ini file format
2018-01-06 15:08:33 +01:00
Brian Warner
097abb42fa
tahoe.cfg: add tub.port=listen:i2p (and/or listen:tor)
...
This delegates the construction of the server Endpoint object to the i2p/tor
Provider, which can use the i2p/tor section of the config file to add options
which would be awkward to express as text in an endpoint descriptor string.
refs ticket:2889 (but note this merely makes room for a function to be
written that can process I2CP options, it does not actually handle such
options, so it does not close this ticket yet)
2017-11-03 00:24:46 -07:00
9375056b61
Split up startstop_node and add 'tahoe daemonize'
...
This sets the stage for further changes to the startup
process so that "async things" are done before we create
the Client instance while still reporting early failures
to the shell where "tahoe start" is running
Also adds a bunch of test-coverage for the things that got
moved around, even though they didn't have coverage before
2017-09-19 10:39:19 -06:00
Gordon Hall
593ebdfb07
add note about using docker compose to running docs
2017-09-19 09:25:39 -07:00
AnBuKu
e453761a0b
Time goes by :-)
...
See https://packages.debian.org/source/stretch/tahoe-lafs
2017-09-18 07:27:09 +02:00
798bf57e28
Add 'tahoe invite' and 'tahoe create-node --join' commands
...
This opens a wormhole and sends appropriate JSON down
it to a tahoe-gui using a wormhole server running on
tahoe-lafs.org
The other end uses the 'tahoe create-node' command (with
new --join option) to read the configuration JSON from
a 'tahoe invite' command
2017-08-08 18:27:06 -06:00
1f16a173f0
flatten the result structure
...
flat is better than nested
2017-07-27 15:32:47 -04:00
e0ee726d22
Update to the format the code now actually produces
2017-07-27 15:28:29 -04:00
