3 ms·
I wonder what someone has against BitBucket... but I also understand that BitBucket is unlikely to share all of whatever they suspect. In such cases, the targe
by gojomo 17y ago
I wonder what someone has against BitBucket... but I also understand that BitBucket is unlikely to share all of whatever they suspect.
In such cases, the target of a DDoS often only has hunches and pseudonymous threats from which to reason about attacker motivations. Airing such speculative info risks (1) unfairly implicating innocents who may have been framed; (2) encouraging the guilty with more attention for their grievances or destructive skills.
- spudlyo 17y agoGoing on nothing other than my overactive imagination, I speculate that somebody hosted exploit code on BitBucket that somebody else didn't want made public. There seems to be a growing trend of black hat security types who are very much against disclosure of exploits and holes.
- pjhyett 17y agoWe (GitHub) were DDoS'd the other week when members of an open source project hosted on the site got upset at the other members and wanted to make the entire ecosystem around the project suffer. Not saying that's what happened to BitBucket, but it could be a similar reason. Talking with Sourceforge, it sounds stuff like this happens fairly regularly. It's one of the disadvantages of running a site that has members capable of doing this stuff.