Exchange strong encrypted messages effectively and privately between two parties.
composer require mnavarrocarter/fernetIt's really easy to get started:
// Instantiate the Fernet class using the static factory and passing the base64url encoded key.
$fernet = MNC\Fernet::create('cw_0x689RpI-jtRR7oE8h_eQsKImvJapLeSbXpwF4e4=');
// Then, you can encode messages with your fernet instance
$token = $fernet->encode('hello');
// You can then decrypt that token back to the original message
$message = $fernet->decode($token);Fernet is a recent not so recent specification for encrypting a message and encode
it into a secure token with established security practices like block sizing, padding and
signature hashing.
Encryption is symmetric using a secret of 32 bytes.
You can read more details about the specification here.
Mainly for three reasons:
Security: The spec has been defined by cryptographers, not developers, with well-known, long-established security practices like message padding, standard block sizing, and signature verification before decryption.
Evolvavility: Every token has a version (the current and only version of Fernet is 0x80). The implementations look at the version to decide how the token will be handled. It's not the user who defines then a set of algorithms, but the spec version. Should common nowadays algorithms become more prone to breaking due advancements in computing power, Fernet can solve this easily by rolling a new version of the Spec.
Convenience: Depending on the message, Fernet tokens can be small. They can fit cookie size constraints easily, can be pasted in urls easily too, and shared in requests headers or bodies without a problem.
Fernet solves all the problems existing with current "industry-standard" solutions for message-exchanging, like the JOSE standards.
I could go on lengthy here, but if you are interested to know why, you can take a look at this article.