Update readme

This commit is contained in:
Les De Ridder 2017-03-19 22:46:05 +01:00
parent 1e89db7d0f
commit b1dfa5435f
No known key found for this signature in database
GPG Key ID: 5EC132DFA85DB372
1 changed files with 3 additions and 2 deletions

View File

@ -6,9 +6,10 @@ salty-ircd is an [Internet Relay Chat](https://en.wikipedia.org/wiki/Internet_Re
The main goals of salty-ircd are strict RFC compliance and security.
### RFC compliance
salty-ircd aims to be fully compliant with the IRC RFCs, specifically [RFC 1459](https://tools.ietf.org/html/rfc1459), [RFC 2811](https://tools.ietf.org/html/rfc2811), [RFC 2811](https://tools.ietf.org/html/rfc2812), and [RFC 2813](https://tools.ietf.org/html/rfc2813) (planned).
salty-ircd aims to be fully compliant with the IRC RFCs, specifically [RFC 1459](https://tools.ietf.org/html/rfc1459), [RFC 2811](https://tools.ietf.org/html/rfc2811), [RFC 2811](https://tools.ietf.org/html/rfc2812), and [RFC 2813](https://tools.ietf.org/html/rfc2813) (planned).
Newer RFCs take precedence over older RFCs.
Any features breaking RFC compliance will be made available through compile-time options.
Any additional features breaking RFC compliance will be made available through compile-time options.
### Security
* salty-ircd will require TLS for all connections. An exception could be made to allow hosting a Tor hidden service.