Sat, 25 Mar 2017 16:45:34 +0100 Philipp Hörist <[email protected]> wrote:
> Its seems you dont like e2e encryption, and maybe you have no use > case for it, but other people have obliviously as many people are > using it. So what's the problem? Use it. > Thats only true if you only use one device. And thats intended as we > dont want people that get our key to decrypt our Archive. its called > Perfect Forward Secrecy. Yeah, tell that a user when he loses his key. This will help him a lot :) > Also i dont see how your UX Problems with Public-key cryptography > have any relevance here. Well, browser developers resolved this UX problem by providing preconfigured CA certificates, so a user doesn't need to decide. I don't see how this is possible with OMEMO. And if it's not possible, then, like someone said on the list before, "a protocol creating UX problems is a bad protocol". > If your solution to Public-key cryptography UX Problems is to use no > encryption at all, it feels like you wasting our time. LOL, but it's you who trying to waste my time because I (or another ejabberd developer) will have to implement this OMEMO stuff :) And I never said "not to use encryption at all". I actually don't care as long as OMEMO is client developers burden. That's why I typically silent on this topic. > Whats your Agenda? Obviously you are not interested in e2e, so just > dont use it. My "agenda" is that I'm against putting OMEMO on the server for the reasons I mentioned, that's it. _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
