From ede21b4e76a7859fd1016c5fbf5c9ab501569e0d Mon Sep 17 00:00:00 2001 From: aewens Date: Mon, 18 Feb 2019 04:40:02 +0100 Subject: [PATCH] Fixed configuration considerations to meet requirements --- draft-tilde-center.md | 12 ++---------- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/draft-tilde-center.md b/draft-tilde-center.md index f78d8da..69e0bfe 100644 --- a/draft-tilde-center.md +++ b/draft-tilde-center.md @@ -597,13 +597,5 @@ network's security. Outside of the configurations already mentioned prior in this document, there 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 -Kademlia DHT of the peer nodes along with the UUID, GPG public key, and domain -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. +For members of the tildeverse (aside from tilde.center and its peers) no +configuration is needed to meet this RFC's request.