Re:Unintended Affordances (or why I believe encrypting every...
by sanxiyn on Thursday April 30, 2015 @11:23AM
(#9465614)
Encryption bundles orthogonal concerns, authenticity and confidentiality. Since there are situations confidentiality is not desired (see OP), I think we should work on making cleartext+signature easier.
[ Parent
| on HN ]
Re:Unintended Affordances (or why I believe encrypting every...
by sqeaky on Thursday April 30, 2015 @11:46AM
(#9465800)
This stance implies that the complexity of having some systems or parts of systems encrypted, but not others is without cost.
I would not be able to teach my grandmother the UI of this system, she has a hard time with chrome's SSL lock icon as it is. Encrypting everything is a great situation for her so she can shop online safely.
Re:Unintended Affordances (or why I believe encrypting every...
by Nursie on Thursday April 30, 2015 @11:27AM
(#9465642)
Set your ciphersuite to RSA_NONE_SHA256...
Re:Unintended Affordances (or why I believe encrypting every...
by ryan-c on Thursday April 30, 2015 @11:41AM
(#9465753)
No common browsers support cipher suites without encryption.
Re:Unintended Affordances (or why I believe encrypting every...
by Nursie on Thursday April 30, 2015 @11:52AM
(#9465845)
True, and this is largely a good thing - if you actually want a secure connection you do not want your browser accepting a NULL cipher suite and saying "Hey! I'm using TLS!"
There's no reason why browser-makers couldn't put in a capability to fetch some resources this way, without telling the user that what thy are doing is 'secure'.
However by the time you've done your RSA verification and a per-packet SHA256 HMAC or similar, the overhead of AES encrypting the data might not actually be all that much more...
Re:Unintended Affordances (or why I believe encrypting every...
by Lawtonfogle on Thursday April 30, 2015 @01:54PM
(#9466567)
What does that solve? They can MITM to modify the clear text and the signature.