ad-assurance - [AD-Assurance] RE: More info on SSL/TLS
Subject: Meeting the InCommon Assurance profile criteria using Active Directory
List archive
- From: Ron Thielen <>
- To: "" <>
- Subject: [AD-Assurance] RE: More info on SSL/TLS
- Date: Thu, 12 Sep 2013 18:16:35 +0000
- Accept-language: en-US
Yes, or you could use something like Fiddler to capture and replay all HTTP(S) traffic.
However, the point of protected channels is to protect the data between the endpoints.
If the threat agent has inordinate access to either endpoint, then it’s game over anyway.
It’s about the channel, not the termination points.
If you want more to worry about with regard to stupid things that can happen at endpoints, look at
http://blog.elliottkember.com/chromes-insane-password-security-strategy Ron From:
[mailto:] On Behalf Of Capehart,Jeffrey D I saw this on the SANS blog and Newsbites and thought it might be interesting reading since we have been talking about SSL and TLS. Just in case you were wondering how hard it might be to decrypt your protected channel, this post goes
into detail showing how easy it is to do. -Jeff C. https://isc.sans.edu/diary/Psst.+Your+Browser+Knows+All+Your+Secrets./16415 “I got to wondering one day how difficult it would be to find the crypto keys used by my browser and a web server for TLS sessions. I figured
it would involve a memory dump, volatility, trial and error and maybe a little bit of luck. So I started looking around and like so many things in life….all you have to do is ask. Really. Just ask your browser to give you the secrets and it will! As icing
on the cake, Wireshark will read in those secrets and decrypt the data for you. Here’s a quick rundown of the steps:” Jeff Capehart, CISA |
- [AD-Assurance] More info on SSL/TLS, Capehart,Jeffrey D, 09/12/2013
- [AD-Assurance] RE: More info on SSL/TLS, Ron Thielen, 09/12/2013
- [AD-Assurance] RE: More info on SSL/TLS, Capehart,Jeffrey D, 09/12/2013
- [AD-Assurance] RE: More info on SSL/TLS, Ron Thielen, 09/12/2013
Archive powered by MHonArc 2.6.16.