Timeline for Why can't I decrypt SSL traffic with the client's private key only?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 23, 2014 at 10:57 | comment | added | DRF | @Wojtek Also quite offtopic, I would like to point out that trying to stay safe from the NSA (or any other large nation state security agency) is probbably a losing battle for any individual. The best you can do is try to minimize your exposure to the large collection methods but if you're being targeted you're pretty much toast. They won't be attacking the crypto if they want to know what you are doing. That's very bad ROI. | |
| Sep 23, 2014 at 10:52 | comment | added | DRF | @Wojtek I haven't had a chance to actually watch the whole video (hopefully in the evening) but from the links and a cursory scan it seems to be about the EC-DRBG hoohaa. That though has nothing to do with ECDHE in itself. It is just a possible backdoor in a random number generator that happens to also use eliptic curves. You can (and most probably do) use any other random number generator for the ECDHE key exchange. The similarity is only in the name. | |
| Sep 23, 2014 at 7:53 | comment | added | Wojtek | A bit offtopic, but... what about ECDHE and youtube.com/watch?v=ulg_AHBOIQU ? Is it still "safe"? | |
| Sep 23, 2014 at 7:26 | review | First posts | |||
| Sep 23, 2014 at 7:43 | |||||
| Sep 23, 2014 at 7:23 | history | answered | DRF | CC BY-SA 3.0 |