Replies: 1 comment
-
Use case: You want to ensure your backups are not spoofed by someone who may have your public key. In this scenario, nobody but the author has the public (and private) keys, so there is no way to spoof anything. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
If one wanted to keep their public key protected by encrypting it by itself (It wouldn't really be a public key then of course), it would offer a more secure way to avoid spoofing of messages by a 3rd party, and other security issues.
To use the public key, you'd have to decrypt it with the private key, of course. That could be done inside Age/Rage without exposing it.
Of course once can already do this either manually or by created some wrappers around Age/Rage.
If there is any merit to this, please discuss.
Beta Was this translation helpful? Give feedback.
All reactions