Timeline for Is my server vulnerable to a perl exploit?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 23, 2016 at 20:29 | history | tweeted | twitter.com/StackSecurity/status/690994735117418496 | ||
| Jan 16, 2016 at 20:34 | comment | added | Ken Sharp | @Pokechu22 That's the one, thanks! I think I tried three spaces. Post edited. | |
| Jan 16, 2016 at 20:34 | history | edited | Ken Sharp | CC BY-SA 3.0 |
Correct formatting
|
| Jan 15, 2016 at 19:58 | comment | added | Pokechu22 | To format as code, you'd need to put 4 spaces before hand. But, that would disable word wrap, which isn't a good idea, so I think leaving as-is would be good. | |
| Jan 15, 2016 at 15:17 | history | edited | Ken Sharp | CC BY-SA 3.0 |
Sentence construct fail
|
| Jan 15, 2016 at 15:15 | comment | added | Ken Sharp | The 200 response certainly does raise eyebrows, even monobrows. | |
| Jan 15, 2016 at 15:14 | vote | accept | Ken Sharp | ||
| Jan 15, 2016 at 13:43 | answer | added | HamZa | timeline score: 7 | |
| Jan 15, 2016 at 13:13 | comment | added | Steffen Ullrich | These are just different user agents probing your server and sometimes looking if an exploit will work. The access log shows only what gets tried and not if you are vulnerable. 200 response might indicate a problem but does not need, it depends on your web site setup, server configuration... | |
| Jan 15, 2016 at 13:03 | history | asked | Ken Sharp | CC BY-SA 3.0 |