Live data from Hacker News

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

twitter.com

231–240 of 476 posts

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

#231
post #218

Earlier quoted context omitted.

Verizon and US courts would disagree with you.

Links? I'm curious about existing case law.

Here's one example: https://www.wired.com/2013/03/att-hacker-gets-3-years/

>The two essentially wrote a program to send GET requests to [publicly available pages on] the web site.

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

#232
post #218

Earlier quoted context omitted.

Links? I'm curious about existing case law.

Here's one example: https://www.wired.com/2013/03/att-hacker-gets-3-years/ >The two essentially wrote a program to send GET requests to [publicly available pages on] the web site.

Ruling was appealed and deemed incorrect: https://www.wired.com/2014/04/att-hacker-conviction-vacated/

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

#233
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.

For the life of me, I can't understand why people insist on making passwords with the name of the company in them. It's so absolutely stupid, but common.

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

#234
post #196

Earlier quoted context omitted.

For example that someone finds out about that backdoor and activate it to spy on users. Forwarding a port in Docker is not magic…

Sure, it's simple. But you would have to be able to modify the container settings anyway. For all practical uses, and certainly in my case, you could just make it run a different image at that point. Or copy another executable into the container and run it. You're already privileged. Requiring you to be privileged to access the debug server means it's secure.

Until things around change and what was previously "a secure backdoor" becomes a "less secure backdoor". ;-)

One can read every second week about cases where some backdoor that was meant to be used "only for debugging" landed in the end product and became a security problem.

Actually I usually suspect malice when something like that is found once again, as "who the hell could be so stupid to deliver a product with a glaring backdoor". But maybe there is something to Hanlon's razor… :-D

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

#235
post #14

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

You can't download from mega.nz unless you have their "downloader" app or an account, or if you have Firefox or Safari. It's useless. The torrent works.

Or if you have OpenSSL and curl...

(At least the last time I had to download from MEGA, I RE'd what it does and it was somewhat clever - AES128 in counter mode, key is in the hash part of the URL.)

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

#236
post #37

Earlier quoted context omitted.

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

Judging from the current, in all likelihood it is the opcode that APEI (a part of ACPI) tables write to port 0xB2 in order to invoke firmware services that run in system management mode.

Comment, not current. :)

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

#237
post #21

Earlier quoted context omitted.

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.

We just rename our files with .novirus on the end. I assume the main point is to stop executables from outside running with a click, or internal forwards of the same by compromised users which is why it's so easy to bypass.

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

#238

Earlier quoted context omitted.

A manufacturer wanted to upgrade one of their equipment lines to be more modern. The developers of the original product, both hardware and software, were no longer with the company. Since they just wanted to add some new features on top and present a better rack-based interface to the user, they decided to build a bigger box, put one of the old devices inside the box, then put a modern PC in there, and just link the…

This can't be real... are you serious? It sounds like one of those silly buisness parabels!

The older I get, the less I care if individual stories like this are true. The fact that they could be is concerning enough :) And they are educational nonetheless.

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

#239

https://twitter.com/deletescape/status/1291422841834016770 Hmm…

I’m completely ignorant about this but is it possible that they’re referring to a “debugging backdoor”?

It's most likely a callback from OS to firmware, or at least this is what I can guess based on the single comment present in the screenshot and what I saw in the past in the APEI tables of Intel-based servers.

APEI tables are a part of ACPI that tell the OS how to write an error record persistently in the machine log, inject a memory error for debugging purposes, and stuff like that that's tied to the RAS (Reliability/Availability/Serviceability) features of a server. The tables contain a list of instructions like "write a value to memory" or "write a value to an I/O port"; the way they work in practice is that, by following these instructions, the OS causes the processor to enter system management mode (that's the "backdoor" into the firmware) where the firmware services the APEI request.

Since the tweet mentions SMM and RAS in the two lines it shows, my guess is that it's related to that functionality.

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

#240
post #118

Earlier quoted context omitted.

No country Will extradite their own citizens, though. If intel wants the person punished, they have to sue them in the country they live in.

> No country Will extradite their own citizens, though. This is demonstrably false. While not all of this list are Canadian citizens, some are: https://en.wikipedia.org/wiki/Category:People_extradited_fro...

Just had to remind of Charles Ng, huh? If you have a weak stomach, don’t dig further.
Post reply on HN