| ... | ... | @@ -2,7 +2,7 @@ |
|
|
|
|
|
|
|
----
|
|
|
|
|
|
|
|
[Fenrir](Fenrir)'s aim is to provide a single, efficient and extremely flexible protocol to manage authentication, authorization and encryption in [federated](Federated_vs_Distributed) environments.
|
|
|
|
**Fenrir**'s aim is to provide a single, efficient and extremely flexible protocol to manage authentication, authorization and encryption in [federated](Federated_vs_Distributed) environments.
|
|
|
|
|
|
|
|
It mimics a lot SCTP or QUIC in terms of transport features, with both reliable and unreliable transmission, but it also includes encryption, [federated](Federated_vs_Distributed) authentication, and a lot of other features, such as cross-domain single sign-on.
|
|
|
|
|
| ... | ... | @@ -45,7 +45,10 @@ There is also a quick [Comparison](Comparison) page if you just want to have a q |
|
|
|
|
|
|
|
## How?
|
|
|
|
|
|
|
|
See the [History](History) to know a little of how the Fenrir protocol was designed.
|
|
|
|
For an technical overview of the protocol read this
|
|
|
|
[paper](https://www.fenrirproject.org/Fenrir/Fenrir_Project/uploads/504146146b8bbd21e0b1d4c40957c825/paper.pdf)
|
|
|
|
that tracks the design of the protocol.
|
|
|
|
|
|
|
|
|
|
|
|
This protocol will be UDP-based, much like Google is doing with their [QUIC](QUIC) protocol
|
|
|
|
In fact, a lot of ideas were taken from both SCTP and QUIC, so we have a full-featured transport protocol that handles cryptography and authentication in a new way. If it was not for the inclusion of a new authentication/authorization/cryptography mechanism, Fenrir would be too similar to google's QUIC.
|
| ... | ... | @@ -89,4 +92,3 @@ The [library code](https://www.fenrirproject.org/Fenrir/libFenrir) is public, ye |
|
|
|
To start coding, please look at the [Development](Development) page.
|
|
|
|
|
|
|
|
Some people might think that there will be problems with software patents. [My position](Software_Patents) on how to deal with those cases is already well defined. |
|
|
|
|
