Timeline for Detecting heartbleed without sending a heartbeat packet (Heartbleed specific)
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 29, 2016 at 20:19 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 29, 2016 at 19:11 | answer | added | Steffen Ullrich | timeline score: 1 | |
| Feb 29, 2016 at 16:24 | comment | added | multithr3at3d | Then test it from a vantage point where it won't be blocked. | |
| Feb 29, 2016 at 16:05 | comment | added | Ouney | One thing to note here is request is blocked by the originating network, so we are not able to distinguish if the request is blocked OR server is really not vulnerable. | |
| Feb 29, 2016 at 16:03 | comment | added | d1str0 | If the packet is already blocked by firewall or software, wouldn't that mean they aren't vulnerable to Heartbleed? | |
| Feb 29, 2016 at 16:01 | history | asked | Ouney | CC BY-SA 3.0 |