Live data from Hacker News

20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions

twitter.com

21–30 of 476 posts

Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions

#21
post #2

> If you find password protected zips in the release the password is probably either "Intel123" or "intel123". This was not set by me or my source, this is how it was aquired from Intel. Can't say I'm surprised, people are lazy. Another large tech company I used to work for commonly used an only-slightly more complex password. But it was never changed, so people who had left the team still could have access to things…

Password protection may have been used to bypass antivirus and other filters. While you should treat dumps like this with a lot of suspicion, treat password protected zips with a heaping dose of care as they may have been used to evade automated defenses.

Yes - but not for hostile purposes, but because your own company's antivirus won't let you mail an executable to a colleague.

Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions

#23
post #16

Is releasing this legal? It seems like this person isn't really disguising their identity or concerned about breaking the law. In their profile they even seem to brag about leaking company's code.

Sometimes people break the law!

Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions

#24
post #11

At 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. :|

Yeah, I think that this is likely the case here from the screenshot.

Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions

#25
post #18

In what ways can an end user of intel processor expect to benefit from this? I'm guessing none, since ever consumer interface is already a standard ... Can anybody chime in?

Optimistically, the exposure of backdoors in the firmware may cause Intel to patch and close them. Realistically, Intel will patch the firmware and replace the backdoors with new ones.

Besides the backdoors I mean, I was thinking about performance or usability improvements...

Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions

#26

In what ways can an end user of intel processor expect to benefit from this? I'm guessing none, since ever consumer interface is already a standard ... Can anybody chime in?

It would be illegal, but some of that code might help Coreboot development.

Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions

#27
post #6

The advice to try a password of “Intel123” on any protected files says it all. This organisation genuinely deserves whatever is coming for them.

This type of passwords are use in almost all big corporations. People are being asked to encrypt things but without password managers or keys management tools.

Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions

#28
post #17
post #16

Is releasing this legal? It seems like this person isn't really disguising their identity or concerned about breaking the law. In their profile they even seem to brag about leaking company's code.

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

#30
post #18

Earlier quoted context omitted.

Optimistically, the exposure of backdoors in the firmware may cause Intel to patch and close them. Realistically, Intel will patch the firmware and replace the backdoors with new ones.

Besides the backdoors I mean, I was thinking about performance or usability improvements...

Other than disabling security features, Intel already publish extensive optimization manuals, so I don't think there's anything to go on here.
Post reply on HN