> 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.
20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions
21–30 of 476 posts
Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions
#22Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions
#23Is 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.
Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions
#24At 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
#25In 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.
Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions
#26In 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?
Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions
#27The advice to try a password of “Intel123” on any protected files says it all. This organisation genuinely deserves whatever is coming for them.
Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions
#28Is 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.
Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions
#29Re: 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions
#30Earlier 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...