tildeverse
/
rfcs
4
6
Fork 6
Code Issues 5 Pull Requests 1 Releases Wiki Activity

Fixed configuration considerations to meet requirements

This commit is contained in:
aewens 2019-02-18 04:40:02 +01:00
parent d7ab49c836
commit ede21b4e76
1 changed files with 2 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
draft-tilde-center.md
View File

@ -597,13 +597,5 @@ network's security.
Outside of the configurations already mentioned prior in this document, there Outside of the configurations already mentioned prior in this document, there
are no other required configurations to consider for the Tilde Center project. are no other required configurations to consider for the Tilde Center project.
The configurations that a peer server needs to be a part of the TCN is a For members of the tildeverse (aside from tilde.center and its peers) no
Kademlia DHT of the peer nodes along with the UUID, GPG public key, and domain configuration is needed to meet this RFC's request.
name / IP address of the peers it communicates directly with. The configurations
needed to send valid GPG+ messages through the dispatcher are a pair of GPG
keys. For facilitate the user accounts in LDAP it needs to be configured to use
TLS for the LDAPS protocol and have the ppolicy enabled to lock accounts to
prevent internal brute force attacks. Lastly, to properly handle the messages
coming from the dispatcher the SQL database on the system should contain the
specified tables and fields within those tables so that the federated data ends
up in the correct place.