GitHub sued for aiding hacking in Capital One breach
1–10 of 104 posts
Re: GitHub sued for aiding hacking in Capital One breach
#2‘The lawsuit also makes a bold claim that "GitHub actively encourages (at least) friendly hacking." It then links to a GitHub repository named "Awesome Hacking.”[0]’
Oh brother.
Re: GitHub sued for aiding hacking in Capital One breach
#3Barriers to posting SSN-like data would make it difficult for a lot of people to do their job. Software that handles SSN info should have fake data for tests.
Re: GitHub sued for aiding hacking in Capital One breach
#4from the thank-god-for-section-230 dept...
Re: GitHub sued for aiding hacking in Capital One breach
#5[deleted]
Re: GitHub sued for aiding hacking in Capital One breach
#6‘The lawsuit also makes a bold claim that "GitHub actively encourages (at least) friendly hacking." It then links to a GitHub repository named "Awesome Hacking.”[0]’ Oh brother. [0] https://github.com/Hack-with-Github/Awesome-Hacking
While I do think that "hacking" is less demonized than it was circa "Hackers", it is not surprising that the attitude around a lawsuit is a little outdated. I'm just glad the target is an entity with sufficient resources to defend such a spurious accusation - a similar suit could probably destroy a smaller company.
Re: GitHub sued for aiding hacking in Capital One breach
#7> The lawsuit said GitHub had an obligation under California law and industry standards to keep off or remove the Social Security numbers and personal information from its site. The plaintiffs believe that because Social Security numbers had a fixed format, GitHub should have been able to identify and remove this data
> The lawsuit alleges that by allowing the hacker to store information on its servers, GitHub violated the federal Wiretap Act.
> The lawsuit also makes a bold claim that "GitHub actively encourages (at least) friendly hacking." It then links to a GitHub repository named "Awesome Hacking." ... not associated with GitHub staff or management, but owned by a user who registered on the platform
This lawsuit is a natural extension of the calls for internet platforms to better police and accept liability for the content they are hosting. These complaints are usually directed towards the big corporations like Google, Facebook and Amazon. But if the rationale is accepted, it will need to be applied universally to startups and SMBs as well. As someone who thinks the world will be a far better place if we had decentralized dumb platforms, as opposed to very centralized platforms with heavy-handed top-down censorship and moderation, I sure hope this movement is turned back.
Re: GitHub sued for aiding hacking in Capital One breach
#8> The lawsuit said GitHub had an obligation under California law and industry standards to keep off or remove the Social Security numbers and personal information from its site. The plaintiffs believe that because Social Security numbers had a fixed format, GitHub should have been able to identify and remove this data > The lawsuit alleges that by allowing the hacker to store information on its servers, GitHub violat…
> As someone who thinks the world will be a far better place if we had decentralized dumb platforms
Then you should be very much in favour of assigning expensive liability to companies running these centralized platforms. If it becomes extremely expensive or legally risky to maintain a big centralized database, that opens a window for free, open source federated protocols to fill that gap.
Consider: You can sue Megaupload Ltd, but you can't sue BitTorrent-the-protocol.
Re: GitHub sued for aiding hacking in Capital One breach
#9Microsoft's lawyers are going to have fun with this one.
Re: GitHub sued for aiding hacking in Capital One breach
#10Barriers to posting SSN-like data would make it difficult for a lot of people to do their job. Software that handles SSN info should have fake data for tests.
Not to mention the pure absurdity of trying to censor numbers.