Timeline for Is client side encryption really better than server side?
Current License: CC BY-SA 3.0
19 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 1, 2018 at 20:02 | answer | added | Fax | timeline score: 0 | |
Jun 1, 2013 at 11:10 | answer | added | hw75 | timeline score: -4 | |
Aug 5, 2012 at 21:39 | vote | accept | Andrei Botalov | ||
Aug 5, 2012 at 15:44 | history | edited | Andrei Botalov |
edited tags
|
|
Jul 11, 2012 at 7:35 | history | tweeted | twitter.com/#!/StackSecurity/status/222957269871104001 | ||
Jul 11, 2012 at 3:20 | answer | added | curiousguy | timeline score: 0 | |
Jul 11, 2012 at 3:05 | comment | added | curiousguy | @Andrey I am pretty sure that your question can be described with this sentence: "web-applications using javascript to perform encryption in web-browsers for added trust", so I added the javascript and web-browsers tags. If by chance I misinterpreted the scope of your question, please remove these tags. | |
Jul 11, 2012 at 3:00 | history | edited | curiousguy |
edited tags
|
|
Jul 11, 2012 at 2:55 | answer | added | D.W. | timeline score: 13 | |
Jul 9, 2012 at 22:19 | history | edited | Andrei Botalov | CC BY-SA 3.0 |
added 11 characters in body
|
Jul 9, 2012 at 17:17 | history | edited | Andrei Botalov |
edited tags
|
|
Jul 9, 2012 at 16:18 | history | edited | Mark Davidson |
edited tags
|
|
Jul 9, 2012 at 15:30 | history | migrated | from ux.stackexchange.com (revisions) | ||
Jul 9, 2012 at 13:21 | comment | added | Andrei Botalov | @BenBrocka In any case Javascript can't be used instead of TLS for encryption as JS code isn't protected from changing at transport level. I asked whether users think that client side encryption is better than server side. | |
Jul 9, 2012 at 13:15 | comment | added | Zelda | @AndreyBotalov eavesdropping doesn't necessarily include local code alterations, that's a much more sophisticated and personal attack vs just sniffing packets | |
Jul 9, 2012 at 12:41 | answer | added | dhmholley | timeline score: 3 | |
Jul 9, 2012 at 12:28 | comment | added | Andrei Botalov | @ChrisF Preventing eavesdroppers from traffic interception is done using Transport Level Security. Client side encryption can't help in it as eavesdropper can modify code that does encryption. | |
Jul 9, 2012 at 12:23 | comment | added | user658 | @AndreyBotalov - the reason to do client side encryption is to secure the data. If you send it in plain text it can be read if the packets are intercepted. | |
Jul 9, 2012 at 12:05 | history | asked | Andrei Botalov | CC BY-SA 3.0 |