Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Encryption of messages - thoughts #31

Open
stolsvik opened this issue Apr 5, 2020 · 0 comments
Open

Encryption of messages - thoughts #31

stolsvik opened this issue Apr 5, 2020 · 0 comments
Labels
thoughts Issues describing some thoughts around a subject

Comments

@stolsvik
Copy link
Contributor

stolsvik commented Apr 5, 2020

Wrt. #30, authentication and non-repudiation: This is the RECEIVING side being able to verify that a message comes from the claimed source, and not someone else that have gotten into the system.

However, it does not hinder another node to fire up and start listening to messages for a given queue - thereby getting information that it should not have had (as the messages still would be plaintext).

Thus, we would need to encrypt messages so that only the intended receiver can read it.

However, this poses a completely different problem than signing: You SIGN with your own (private) key, which then always is the same. With encryption, you would have to ENCRYPT with the receivers (public) key. Therefore, you would need to know which app listens to any given queue.

Thus, you need a registry: #29

@stolsvik stolsvik transferred this issue from another repository Sep 27, 2021
@stolsvik stolsvik changed the title Encryption of messages - thougths Encryption of messages - thoughts Sep 27, 2021
@stolsvik stolsvik added the thoughts Issues describing some thoughts around a subject label Sep 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
thoughts Issues describing some thoughts around a subject
Projects
None yet
Development

No branches or pull requests

1 participant