Added further specifications on configurations
parent
2acd257a26
commit
d7ab49c836
|
@ -595,4 +595,15 @@ network's security.
|
||||||
### Configuration Considerations {#config}
|
### Configuration Considerations {#config}
|
||||||
|
|
||||||
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
|
||||||
|
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.
|
||||||
|
|
Loading…
Reference in New Issue