-
Notifications
You must be signed in to change notification settings - Fork 16
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
"ephemeral" key doesn't achive anything (in the context of ssb) #6
Comments
If we used long term keys like this, the api could treat this as only using symmetric keys. Since we decrypt the my laptop can do 2297 scalarmults a second, but can do 342,916 failed That means we can use more types of decryption and more importantly, use more groups etc. |
Interesting. If we get some kind of concept of fractal identities or shared if you want, then maybe that allows these kinds of ephemeral messages. |
@arj03 sorry I don't follow, can you expand on that a bit? |
I mean that if instead og "me" being one feed, then for groups or specific conversations i can use a different feed, meaning if they break that feed they can only see those messages. This might be rather hypothetical if its the same machine but for a mobile / computer shared identity it might make sense. How this would work in detail i am not sure, but if it maks sende then i dont see why it couldnt be built. |
Yes, well if you both delete your private keys then that is forward secret. This means even you won't be able to open those messages, though. So you could create temporary keys, send them to each other in a private message, then plan your surprise party, then delete your keys. that would be forward secret (but not denyable if the private message was compromised) |
You can't have forward security if you have persistent records.
There is a time and place for denyable communications and a place for on-the-record.
For example, we may socialize over beer while negioating a business deal (denyable, and beer improves denyability), but when we sign the contract the agreement is fully on the record (although, likely private to the participants)
If you used
private-box
in isolation, and disposed of old messages, it would indeed be forward secure.but in ssb it's not, so, we wouldn't loose any security by removing the ephemeral key, and instead using
box(key, sender.secret*recipient.public, ...)
etc.The text was updated successfully, but these errors were encountered: