... | ... | @@ -9,7 +9,7 @@ The result is an efficient, flexible protocol whose aims are the security and th |
|
|
|
|
|
You can follow news on the development here and on **[the Fenrir blog](https://www.fenrirproject.org/blog)**
|
|
|
|
|
|
The protocol can handle unicast, multicast, ordered, unordered, reliable and unreliable transmission, or any combination, with multiple data streams per connection. The federated authentication included grants the interoperability between servers, and introduces the concept of [authorization lattice](https://www.fenrirproject.org/Fenrir/Fenrir_Project/wikis/Federation_Details#introducing-the-authorization-lattice) where we can order multiple privilege levels. Finally the whole project does not rely on the certificate authority model, so no [X.509](X.509) certificates are needed: the keys are derived from DNSSEC.
|
|
|
The protocol can handle unicast, [Multicast](Multicast), ordered, unordered, reliable and unreliable transmission, or any combination, with multiple data streams per connection. The federated authentication included grants the interoperability between servers, and introduces the concept of [authorization lattice](https://www.fenrirproject.org/Fenrir/Fenrir_Project/wikis/Federation_Details#introducing-the-authorization-lattice) where we can order multiple privilege levels. Finally the whole project does not rely on the certificate authority model, so no [X.509](X.509) certificates are needed: the keys are derived from DNSSEC.
|
|
|
|
|
|
Check the [comparison](Comparison) page for a quick glance.
|
|
|
|
... | ... | |