News for hackers. Stuff that matters.
Re:Decrypting TLS Browser Traffic with Wireshark by scintill76 on Friday February 13, 2015 @03:55AM (#9043477)
This does seem, at the least, irresponsible of the browser vendors. I'll be especially angry if Chrome doesn't have very prominent warnings, considering they harass some developers and power users with a warning about an "insecure" configuration Google basically forced them to use.[0] By analogy, I expect nothing less than a blinking red warning covering the entire browser window whenever keys are being logged because of an environment variable.

I also don't think readers should be encouraged so readily to put this into the persistent global environment.

[0] https://code.google.com/p/chromium/issues/detail?id=337734

Re:Decrypting TLS Browser Traffic with Wireshark by reubenmorais on Friday February 13, 2015 @05:57AM (#9043745)
Chrome uses NSS, so the GP applies exactly to it: https://code.google.com/p/chromium/codesearch#chromium/src/n...