Skip to content

Commit 69d18ae

Browse files
committed
Add a note about encryption
1 parent 84581c3 commit 69d18ae

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

ENCRYPTION.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# A note about age encryption in HashUp
2+
3+
The age encryption used when encrypting NATS messages isn't a suitable encryption method, as it lacks some desired properties for message exchange:
4+
5+
> Indeed, we don't want people to use age for messaging, because it would be a pretty lousy messaging encryption tool: no forward secrecy, no ratcheting, no authentication... age is optimized for file encryption, so the occasional reminder of that is something we want to keep, although I agree PAYLOAD would be a good generic word.
6+
7+
From age author in https://github.com/FiloSottile/age/discussions/236#discussioncomment-628046
8+
9+
With that in mind, NATS can use [mutual TLS](https://docs.nats.io/running-a-nats-service/configuration/securing_nats/auth_intro/tls_mutual_auth) on top of the message payload encryption HashUp does with Age, which is probably good enough when both are combined.

0 commit comments

Comments
 (0)