It appears to be caused by a known DoS bug in the Tor Browser Bundle that was patched 4 months ago:
https://trac.torproject.org/projects/tor/ticket/10905 https://trac.torproject.org/projects/tor/ticket/9901 Given the method of triggering the bug - when no Content-Type header is specified and more than 512 bytes of content are sent - it seems unlikely that LinkedIn was intentionally DoSing the Tor Browser Bundle users; that's simply how they chose to configure their web server - for all clients, not just those using the Tor Browser Bundle. Mustafa On 30/06/14 14:04, s.g.dav...@lse.ac.uk wrote: > Hello all, > For some time now I've been concerned about the inability of many Tor users > to access LinkedIn - and more importantly, the fact that attempting to use > LinkedIn results in a fatal freeze. It seems to me that something isn't right > here, so I've written a short piece on it. I'd be grateful for any thoughts > you have. > http://www.privacysurgeon.org/blog/incision/has-linkedin-launched-a-borderline-denial-of-service-attack-against-tor/ > > Best wishes > > Simon > > _________________________ > > Simon Davies > Associate Director > LSE Enterprise > The London School of Economics > > Founder, > Privacy International > > privacysurgeon.org > > s.g.dav...@lse.ac.uk > > Please access the attached hyperlink for an important electronic > communications disclaimer: http://lse.ac.uk/emailDisclaimer > -- Liberationtech is public & archives are searchable on Google. Violations of list guidelines will get you moderated: https://mailman.stanford.edu/mailman/listinfo/liberationtech. Unsubscribe, change to digest, or change password by emailing moderator at compa...@stanford.edu.
