jwt
jwt copied to clipboard
Documentation and code is incorrectly stating that encryption is being used.
The readme states that both "symmectric encryption" and "asymmetric encryption" is being used.
This is wrong. The algorithms used do not encrypt, they do hash, or sign, the values. However the values remain as clear text, just base64-encoded. They cannot be manipulated this way (only if you use "none" as the signing method), but are open to everyone to read.
This documentation fault is replicated in the namespace of so called Encryption
classes, which are only Hashing
or Signing
classes.
Quite right. TBH I don't know how I've never noticed that before. Will look at updating docs. Changing namespaces will have to wait until v2, as modifying namespaces would result in a breaking change.