Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I don't think you would ever want to choose a complicated protocol like Signal if you were not intimately familiar with how it worked. There would be a lot of ways for things to go wrong. If you understood the problem that well you are probably safer doing something simple targeted to your particular problem.

You don't need all the crypto features all the time.

Added: A good example based on the suggested need for forward secrecy. Forward secrecy only protects against the disclosure of a private key. In almost all cases, the ability to get a private key is going to mean that you also get any saved messages. So if your chat application requires the long term storage of old messages then you can skip the forward secrecy part.



It's more important property is keeping messages that are scooped up by malevolent 3 letter agencies secure if a random message in the middle is cryptographically broken.


Forward secrecy does not protect against a break of the cryptography.


No, but it does multiply the cost. It means instead of breaking one key per conversation, there would be many. That could be the difference required.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: