Timeline for How to explain Heartbleed without technical terms?
Current License: CC BY-SA 3.0
33 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2014 at 19:07 | vote | accept | user36976 | ||
| Apr 18, 2014 at 16:09 | comment | added | AShelly | The web server is like an iced-over pond. Your data is the fish, it's protected by the solid layer of ice. But someone just discovered the ice drill and is now able to throw a line in and pull out random stuff. Like maybe your password. | |
| Apr 16, 2014 at 21:57 | comment | added | corsiKa | Not a single answer with "Marco - Polo"? Vote to close... | |
| Apr 16, 2014 at 20:28 | comment | added | Pharap | upload.wikimedia.org/wikipedia/commons/thumb/c/cb/… | |
| Apr 15, 2014 at 2:03 | comment | added | jfa | @supercat how about, "It's an exploit that allows an attacker to request private information out of memory?" | |
| Apr 14, 2014 at 22:27 | comment | added | supercat | @JFA: How about "OpenSSL includes a command which says, essentially, "Think about these 23 bytes of data; tell be the last 23 bytes of data you've been thinking about", but allowing other numbers to substitute for 23. A typical HeartBleed attack message would "Here's 2 bytes to think about; now tell me the last 65,000 bytes you've been thinking about." | |
| Apr 14, 2014 at 18:23 | comment | added | jfa | I showed a fellow computer engineering student the xkcd comic, but since he had no knowledge of encryption keys, https, ssl, and servers, the comic really did nothing for him. I like the first comment, only I'd say it like, "Heartbleed allows a user to take data from whatever the server is doing at that time, including passwords, encryption keys, and personal information, putting all private information at risk." | |
| Apr 13, 2014 at 19:21 | answer | added | Lightness Races in Orbit | timeline score: 1 | |
| Apr 12, 2014 at 13:39 | answer | added | Rich Bradshaw | timeline score: 23 | |
| Apr 11, 2014 at 13:53 | history | protected | Rory Alsop♦ | ||
| Apr 11, 2014 at 13:18 | comment | added | Peter Wone | Same as the last 50000 Windows unchecked buffer length attacks, only this proves it's not just Windows. | |
| Apr 11, 2014 at 12:15 | history | edited | user36976 | CC BY-SA 3.0 |
[Edit removed during grace period]
|
| Apr 11, 2014 at 10:15 | comment | added | alexwlchan | I liked the explanation by Maciej Cegłowski on the Pinboard blog: blog.pinboard.in/2014/04/heartbleed_and_pinboard | |
| Apr 11, 2014 at 7:45 | comment | added | Veda | The easiest way of explaining: xkcd.com/1354 | |
| Apr 11, 2014 at 6:48 | answer | added | Uwe Keim | timeline score: 347 | |
| Apr 10, 2014 at 16:19 | answer | added | user27909 | timeline score: 4 | |
| S Apr 10, 2014 at 16:18 | history | suggested | samthebrand | CC BY-SA 3.0 |
A quick copyedit
|
| Apr 10, 2014 at 16:07 | review | Suggested edits | |||
| S Apr 10, 2014 at 16:18 | |||||
| Apr 10, 2014 at 15:18 | vote | accept | user36976 | ||
| Apr 10, 2014 at 15:25 | |||||
| Apr 10, 2014 at 15:18 | vote | accept | user36976 | ||
| Apr 10, 2014 at 15:18 | |||||
| Apr 10, 2014 at 12:17 | answer | added | SPRBRN | timeline score: 167 | |
| Apr 10, 2014 at 11:53 | history | edited | user36976 | CC BY-SA 3.0 |
deleted 1 characters in body
|
| Apr 10, 2014 at 11:02 | vote | accept | user36976 | ||
| Apr 10, 2014 at 15:18 | |||||
| Apr 10, 2014 at 10:19 | answer | added | Kiwy | timeline score: 2 | |
| Apr 10, 2014 at 10:14 | answer | added | user16214 | timeline score: 11 | |
| Apr 10, 2014 at 9:26 | answer | added | Nzall | timeline score: 3 | |
| Apr 10, 2014 at 8:39 | answer | added | Mark | timeline score: 44 | |
| Apr 10, 2014 at 8:07 | history | tweeted | twitter.com/#!/StackSecurity/status/454168752914194432 | ||
| Apr 10, 2014 at 7:30 | answer | added | dr jimbob | timeline score: 164 | |
| Apr 10, 2014 at 6:45 | answer | added | user44002 | timeline score: 3 | |
| Apr 10, 2014 at 5:59 | comment | added | Darsstar | You could let them watch youtube.com/watch?v=rE5dW3BTpn4 | |
| Apr 10, 2014 at 5:27 | comment | added | makerofthings7 | Heartbleed allows an attacker to anonymously download a random chunk of memory of the server. This means they can get unencrypted passwords, and low-level encryption keys that protect your account... not to mention that an attacker might be able to access any part of the website (or data that you post into that site) | |
| Apr 10, 2014 at 5:21 | history | asked | user36976 | CC BY-SA 3.0 |
