News for hackers. Stuff that matters.
Re:XSS vulnerability found in Github by durin42 on Monday December 20, 2010 @08:47AM (#2024243)
That actually sounds like an awful way to report an XSS. Honestly, as someone that maintains a web service I have to say I'd prefer private disclosure than even the rickroll approach. All it takes is one "genius" doing some copy-paste action and then you're in a world of hurt and damage control.
Re:XSS vulnerability found in Github by mike-cardwell on Monday December 20, 2010 @09:13AM (#2024310)
Regarding this and the other response to me. I would never do what I described. I was just trying to demonstrate to those that don't understand XSS properly, that these issues are serious. I don't think a Rick Rolling really gets that issue across.

If I do an XSS attack against you on github whilst you are logged in, I can compromise all of your source repositories, your code, and in turn, potentially compromise the systems of your users.

Re:XSS vulnerability found in Github by durin42 on Monday December 20, 2010 @10:04AM (#2024468)
End-users aren't who you need to tell. Just site owners. Posting this to HN before it was fixed constitutes (IMO) completely irresponsible disclosure.
Re:XSS vulnerability found in Github by mike-cardwell on Monday December 20, 2010 @10:37AM (#2024586)
I agree. I would not have disclosed this particular XSS flaw until after it was fixed.
Re:XSS vulnerability found in Github by Stuk on Monday December 20, 2010 @05:28PM (#2026029)
Yes, soon after posting I realised it wasn't the best idea I've ever had. I regret posting this before the Github guys got a chance to fix the hole. Not something I'm going to repeat.
Re:XSS vulnerability found in Github by vulf on Monday December 20, 2010 @07:28PM (#2026391)
You should report to [email protected] next time.