News for hackers. Stuff that matters.
Re:U.S. Coding Website GitHub Hit with Cyberattack by pyre on Sunday March 29, 2015 @01:37PM (#9285679)
> > The first round was cross-domain JavaScript, stopped with an "alert()".

> Second round was cross-domain <img>, stopped with referrer.

It does not mention that the alert() used the referrer.

Re:U.S. Coding Website GitHub Hit with Cyberattack by hifier on Sunday March 29, 2015 @01:49PM (#9285721)
Apologies if I'm being dense, but is there some technical reason why it does not use the referrer to selectively block this traffic rather than blocking it for everyone?
Re:U.S. Coding Website GitHub Hit with Cyberattack by pyre on Sunday March 29, 2015 @02:55PM (#9285980)
The content doesn't seem to be blocked if you remove the trailing slash. I don't really have an answer for you aside from that though.

E.g.:

- This works: https://github.com/greatfire

- This doesn't: https://github.com/greatfire/

So far as I know, most links (external or internal) to a Github user's page do not use the trailing slash, so the effects would presumably be minimal.

Re:U.S. Coding Website GitHub Hit with Cyberattack by jurre on Sunday March 29, 2015 @04:33PM (#9286377)
Parsing the referrer would still require some work from their servers right?
Re:U.S. Coding Website GitHub Hit with Cyberattack by hifier on Sunday March 29, 2015 @05:06PM (#9286478)
Sure. I suppose that could be the reason. However, something like HA proxy[1] and (IIRC) CDNs like Akamai can be configured to inspect the headers and take various action.

[1] http://cbonte.github.io/haproxy-dconv/configuration-1.5.html...