News for hackers. Stuff that matters.

A comment on Why Isn’t Telegram End-to-End Encrypted by Default (2017). Parent comment

Re:Why Isn’t Telegram End-to-End Encrypted by Default (2017) by pmlnr on Monday January 11, 2021 @04:31PM (#25737462)
I agree. The part I don't see is then what plugin should handle which part, and how.

Most XMPP clients are plugin based as well. Should the OMEMO plugin then look for aesgcm:// urls, download it, and decrypt it, or should the http upload plugin look for the availability of encryption and try to decrypt?

[ Parent | on HN ]
Re:Why Isn’t Telegram End-to-End Encrypted by Default (2017) by m4lvin on Wednesday January 13, 2021 @11:35AM (#25764322)
That is only a question if HTTP upload and OMEMO are different plugins. With https://dino.im/ it also "just works" and as a user I do not care which part pf the program does what.
[ Parent | on HN ]
Re:Why Isn’t Telegram End-to-End Encrypted by Default (2017) by xorcist on Monday January 11, 2021 @05:42PM (#25738689)
Client authors should do what Conversations do. End users should probably stick with Conversations, for now.

There will always be hacky and badly implemented clients. It comes with the idea of an open specification. That doesn't mean we should use them as a point of comparison.

[ Parent | on HN ]