Timeline for HeartBleed - How to detect compromised websites
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 11, 2014 at 8:24 | comment | added | lorenzog | It would be nice to have a firefox/chrome extension that warns you when the website you're visiting sends content to a vulnerable SSL server... | |
| Apr 10, 2014 at 15:05 | vote | accept | dr jimbob | ||
| Apr 10, 2014 at 11:00 | answer | added | Manoj U | timeline score: 0 | |
| Apr 9, 2014 at 4:10 | answer | added | Anti-weakpasswords | timeline score: 5 | |
| S Apr 8, 2014 at 22:41 | history | suggested | ack__ | CC BY-SA 3.0 |
Edited title so that it reflects better the question
|
| Apr 8, 2014 at 22:40 | review | Suggested edits | |||
| S Apr 8, 2014 at 22:41 | |||||
| Apr 8, 2014 at 16:44 | answer | added | ack__ | timeline score: 4 | |
| Apr 8, 2014 at 16:37 | comment | added | Iszi | There are ways to determine whether a site is currently vulnerable, but what makes this issue so critical is that sites which are not currently vulnerable (but were in the past) may have been exploited before. There's no way for system administrators to know if their site has been previously exploited, and there is no way for users to tell if there's a MitM who's exploited a site because the attacker would be using the legitimate original certificates. | |
| Apr 8, 2014 at 16:29 | history | asked | dr jimbob | CC BY-SA 3.0 |