Live data from Hacker News

The Google plasma globe affair of 2012

lcamtuf.coredump.cx

11–20 of 103 posts

Re: The Google plasma globe affair of 2012

#11
Reading articles like this always causes me to think two things:

1. If this is what a couple of smart guys can do as, essentially, a side project then I can only imagine what nation states with teams of people like this can accomplish.

2. I get why some orgs pour wax into the USB ports of their desktop machines.

Re: The Google plasma globe affair of 2012

#12
post #7

Earlier quoted context omitted.

The other nifty thing about the plasma globe is that immediately after someone plugs it in, they are likely to be too distracted by the luminous fingers of writhing plasma to notice the shell window popping up briefly on the monitor. Nicely-executed hack on multiple levels. For the same reason, waiting a few minutes to pop up the shell, as the article says they did, actually seems counterproductive. It might have bee…

A power user wouldn't (shouldn't) expect a device merely using USB for power to pop up anything on the PC it's plugged into. That would be a dead giveaway that it's doing something it shouldn't be doing.

I think that train left the station when they plugged a 50,000-volt EMI generator into a USB jack. :)

Re: The Google plasma globe affair of 2012

#13
post #6

> The solution proved to be simple: we "borrowed" the USB vendor and product ID sent by an Apple-made keyboard taken from a coworker's desk. Looking at the prototype plasma globe sitting in my "old projects" box, it seems that we picked 05ac:024f. I'm a bit put out that that worked, although I'm struggling to think of a solution that doesn't involve going full-crypto (including a proper PKI to let vendors sign device…

You have to realize that it was never meant to be a security measure. It's only there to identify the device to the host system.

Indeed, and the Keyboard Setup Assistant was never meant to be a security measure, either.

Re: The Google plasma globe affair of 2012

#14

> The solution proved to be simple: we "borrowed" the USB vendor and product ID sent by an Apple-made keyboard taken from a coworker's desk. Looking at the prototype plasma globe sitting in my "old projects" box, it seems that we picked 05ac:024f. I'm a bit put out that that worked, although I'm struggling to think of a solution that doesn't involve going full-crypto (including a proper PKI to let vendors sign device…

It's got the same functionality as an Accept-Encoding HTTP header. It's meant to provide some information to the far end so that it can drive better behaviour. You can "impersonate" a client that isn't compatible and get junk data and there's no cryptographic protection against that.

Re: The Google plasma globe affair of 2012

#15
post #4

>Another critical optimization boiled down to realizing that the response packet allows up to six keycodes to be reported at once. This might have seemed like a straightforward 6x speed gain, but not so: on MacOS, the keystrokes were dequeued not in the order they appeared in the packet, but from the numerically lowest scancode to the highest. This mind-boggling quirk [...] Reporting multiple keys down in the same pa…

That seems like behavior that had to be actively added though, and I am extremely curious why.

Re: The Google plasma globe affair of 2012

#16
post #6

Earlier quoted context omitted.

You have to realize that it was never meant to be a security measure. It's only there to identify the device to the host system.

Indeed, and the Keyboard Setup Assistant was never meant to be a security measure, either.

Ah, that was a mistake on my part: I'd initially thought it was. Rereading that screenshot, it's clear that it's not a security measure, just trying to help the user set the keyboard up, in which context it makes sense.

Re: The Google plasma globe affair of 2012

#17
Emulating keyboards pretty old technique. I feel like the rubber ducky stuff and the likes were around earlier. And they are still popular, the flipper zero has a mode of usb payloads but that's more useful if you have physical access.

Re: The Google plasma globe affair of 2012

#19

Reading articles like this always causes me to think two things: 1. If this is what a couple of smart guys can do as, essentially, a side project then I can only imagine what nation states with teams of people like this can accomplish. 2. I get why some orgs pour wax into the USB ports of their desktop machines.

That was not a side project from my limited understanding ;) I believe the M$/Alphabet/Meta security teams are probably more advanced or on par with the best state sponsored teams. I could be wrong, plus the state sponsored teams might have infiltrated the FAANG security teams ;)

However, I think the FAANG companies act somewhat more restricted. Three letter agencies don't have qualms about things like "chloroforming security guards" and such.

Also, use USB Data Blocker dongles where possible.

Re: The Google plasma globe affair of 2012

#20
post #7

Earlier quoted context omitted.

The other nifty thing about the plasma globe is that immediately after someone plugs it in, they are likely to be too distracted by the luminous fingers of writhing plasma to notice the shell window popping up briefly on the monitor. Nicely-executed hack on multiple levels. For the same reason, waiting a few minutes to pop up the shell, as the article says they did, actually seems counterproductive. It might have bee…

A power user wouldn't (shouldn't) expect a device merely using USB for power to pop up anything on the PC it's plugged into. That would be a dead giveaway that it's doing something it shouldn't be doing.

I’m pretty desensitized to window’s CMD prompts popping up when I install a program or plug in a device. My Razer keyboard even installs borderline malware when you plug it in.

However, if this happened on my Mac I would immediately be skeptical.

Post reply on HN