Someone have a mirror? Seems the actual files are here: https://t.me/exconfidential/590 Edit: files are here https://mega.nz/folder/CV91XLBZ#CPSDW-8EWetV7hGhgGd8GQ or magnet:?xt=urn:btih:38f947ceadf06e6d3ffc2b37b807d7ef80b57f21
The countries of origin of the peers downloading that torrent is pretty cool to see. A fairly broad cross-section of the world.
20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions
71–80 of 476 posts
Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions
#72Earlier quoted context omitted.
Of course it's not legal. This is exfiltrated intellectual property being shared without license.
Which country laws does apply? Is it really illegal to share this in the whole world? Im not so sure about that.
At the very least, Intel owns the copyright on this material, so sharing it is a copyright violation in any country that is a signatory to the Berne Convention or the TRIPS Agreement, which is effectively almost the entire planet.
Then you have to add Trade Secret laws on top of that, which will have slightly narrower jurisdiction but still impact a lot of countries. There are very few places on earth where you would not be facing any legal trouble whatsoever for releasing this material.
Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions
#73At a previous workplace we had a few places in the code which used the word backdoor. It was not an actual backdoor though, but merely a debugging server that could be enabled and allowed you to inspect internal state during runtime. At some point I removed the word backdoor, fearing it would get to a customer or during an audit someone would misunderstand. :|
Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions
#74Earlier quoted context omitted.
Of course it's not legal. This is exfiltrated intellectual property being shared without license.
Is the person publishing this liable or just their source? Because this seems to be a hobby for the person publishing it and yet they also aren't concealing their identity. They list their former employer on their website.
Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions
#75Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions
#76Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions
#77Earlier quoted context omitted.
Yes. Whenever I email or transfer a zip via any method really I always put a basic password on it. I've been bitten way too many times by dumb filters that pick some file out of the zip and declare that it is malicious. I also don't trust messenger apps to not pull my files out and do who knows what with them. A basic password prevents this junk 99% of the time for almost no effort. It won't stop a determined system…
Gmail doesn't seem to like archives it can't open :/
Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions
#78Intel denies it was hacked: https://twitter.com/TheRegister/status/1291461942624677889
... They're claiming it came from an NDA'd source of IP that's shared with customers. Given that it _appears_ like there are backdoors in this Firmware code, we can conclude that if there are such backdoors then they were shared with numerous customers. That really doesn't improve the optics of the breach.
Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions
#79At a previous workplace we had a few places in the code which used the word backdoor. It was not an actual backdoor though, but merely a debugging server that could be enabled and allowed you to inspect internal state during runtime. At some point I removed the word backdoor, fearing it would get to a customer or during an audit someone would misunderstand. :|
When we talk about CPU it's bad enough. Think that your program has an input and output streams where most of the app data goes through and I can attach debugger and listen on the data.
I would not be very happy about it and would still consider it backdoor.