News for hackers. Stuff that matters.

A comment on Anatomy of an Attack: How I Hacked StackOverflow (2012). Parent comment

Re:Anatomy of an Attack: How I Hacked StackOverflow (2012) by ohashi on Sunday July 26, 2015 @08:30PM (#9952763)
What is strange about it? Fast should be clear. Responsive I'm guessing indicates they talked it over (related to fast probably). And reasonable I'm guessing means didn't threaten to sue him for hacking SO and accepted their mistake and wanted to fix it.
[ Parent | on HN ]
Re:Anatomy of an Attack: How I Hacked StackOverflow (2012) by adamconroy on Monday July 27, 2015 @09:51PM (#9959091)
Its the expectation / perspective he had. He is talking like someone who had to report the problem, who had to have his issue resolved and was really pleased with the service.

Its not like he just bought an iPhone which had a flaw and he was happy with the customer service that resolved the issue, but it reads like that.

To be more blunt, he is using rhetoric in his article, probably acquired through osmosis from reading other articles, without actually realizing that the rhetoric doesn't apply to his situation.

[ Parent | on HN ]
Re:Anatomy of an Attack: How I Hacked StackOverflow (2012) by LunaSea on Monday July 27, 2015 @02:35AM (#9953699)
Too bad that StackOverflow doesn't have an official bug bounty or even a wall of fame.
[ Parent | on HN ]
Re:Anatomy of an Attack: How I Hacked StackOverflow (2012) by esnard on Monday July 27, 2015 @05:22AM (#9954182)
They actually have a wall of fame: http://stackexchange.com/about/security
[ Parent | on HN ]
Re:Anatomy of an Attack: How I Hacked StackOverflow (2012) by LunaSea on Monday July 27, 2015 @07:13AM (#9954476)
It's not accurate though. I found a vulnerability on StackExchange too and am not listed although it was fixed.

Also I'm pretty sure that I've read much more StackExchange vulnerabilities as there are listed here.

[ Parent | on HN ]