by joushx on 9/15/13, 12:18 PM with 34 comments
by fooyc on 9/15/13, 1:09 PM
The message is sent through HTTPS anyway.
If HTTPS was compromised, the javascript code signing the message, and the signing key, and everything related to handling the clear text message would be compromised too anyway.
This is redundant with HTTPS, but also useless if HTTPS is MITM.
by y0ghur7_xxx on 9/15/13, 1:29 PM
I know, for a contact form this is very unlikely, but just from a security point of view, if I would write something like this, I would host js loaded by the page on my own server.
by JosephRedfern on 9/15/13, 12:43 PM
by eli on 9/15/13, 2:43 PM
You've added a fair bit of complexity for no specific benefit; likely a net loss in terms of security.
by mfwoods on 9/15/13, 1:10 PM
The way to intercept the message with the server doing PGP would be to either MITM the connection or breach into the server to intercept before encryption.
In both cases you could just as well modify the javascript served to the browser to defeat the PGP done in the browser as well.
by cheyne on 9/15/13, 4:51 PM
by sambeau on 9/15/13, 1:21 PM
by aluhut on 9/15/13, 2:21 PM
I hope the issue of usability gets more attention in future security tool development.
by st00pid on 9/15/13, 2:27 PM
by mschuster91 on 9/15/13, 12:26 PM
by rorrr2 on 9/15/13, 12:54 PM
I'm too lazy to parse their JS code.