ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2025-04-07 10:56:49 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

clean up the description of the tls usage

Browse Source
This commit is contained in:
Jean-Paul Calderone 2018-05-22 09:00:10 -04:00
parent 65103445ea
commit ab37b5eabb
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/proposed/http-storage-node-protocol.rst
View File

@ -79,10 +79,10 @@ This protocol aims to satisfy the above requirements at a lower level of complex
Communication with the storage node will take place using TLS.
The TLS version and configuration will be dictated by an ongoing understanding of best practices.
The only requirement is that the certificate have a valid signature.
The storage node will publish the corresponding Subject Public Key Information hash (SPKI hash)
(e.g., via an introducer).
The SPKI hash will constitute the storage node's identity.
The storage node will present an x509 certificate during the TLS handshake.
Storage clients will require that the certificate have a valid signature.
The Subject Public Key Information (SPKI) hash of the certificate will constitute the storage node's identity.
The **tub id** portion of the storage node fURL will be replaced with the SPKI hash.
When connecting to a storage node,
the client will take the following steps to gain confidence it has reached the intended peer: