> TEMPEST [1] (or Van Eck Phreaking) is a technique to eavesdrop video monitors by receiving the electromagnetic signal emitted by the VGA/HDMI cable and connectors
> GNU Radio [2] is a Free & Open-Source Toolkit for Software Radio
>> TEMPEST [1] (or Van Eck Phreaking) is a technique to eavesdrop video monitors by receiving the electromagnetic signal emitted by the VGA/HDMI cable and connectors
IIRC, I think it originally used the analog signals generated by controlling the electron gun in a CRT.
tl;dr The signal from a DVI cable can be detected but at much more reduced ranges. See also; RAGEMASTER (Snowden leak) a range extending implant for video cables.
TEMPEST was also the codename of the NSA project for leveraging emissions. And it has become code for machines modified to protect against such things. So a "tempest computer" (if you ever see one) is a computer hardened against emissions.
I've heard about them being used for an opposite reason. Rather than for security, they are used in places where you don't want to risk them interfering with other equipment, like a room with radar equipment that might be sensitive.
> TEMPEST [1] (or Van Eck Phreaking) is a technique to eavesdrop video monitors by receiving the electromagnetic signal emitted by the VGA/HDMI cable and connectors
I've always thought of TEMPEST as magic and incredibly cool. I get how this works for video, but why is it that infosec recommends for EM shielding of a datacenter? Wouldn't there be so much EM noise from a DC that the data you could pull off be .. noisy? lossy?
It's difficult, but it gets a lot easier if you can send requests in. If you can force some kind of deterministic (not salted) crypto calculation to happen with a particular piece of key material, over and over again, you can use the same correlation technique that works for extracting GPS signals from hundreds of dB below the noise floor.
People have also done this with analysis of the power consumption of crypto hardware. I believe this was used against Trezor devices.
My old boss always said "There isn't 200 dB in the entire universe". Of course if you compare the diameter of the universe to a quark, it's 10,453 dBmeters, so I guess there is.
Every 3dB is roughly a halving of the power level. It's hard to wrap a human brain around the orders of magnitude difference, the numbers are so far outside of anything we can encounter in the human scale.
Still, I will try to make an analogy. Start with the smallest transistor we make today, (7nm) and scale it up by the equivalent of 200dB and it would be 258 million km across, or about the same as the diameter of the Earth's orbit around the sun.
That's a pretty good rule of thumb until you get into some really weird stuff.
The link budget for bouncing radio signals off the moon (EME) is something like 260 dB. A while ago I had a chance to see the ground station at NASA Goldstone where they manage the radio links to Mars and the outer planets. There was a terminal open with ~single digit bits / second coming in from one of the Voyager probes. Having a 70 meter dish and a cryogenic receiver helps, but the link budget there has got to be truly staggering...
My old boss worked on the Apollo mission comms, specifically the large dish antennas on the ship. It was just his way of joking about large numbers.
10 dB (deci-Bells) is an order of magnitude ratio; 10 dB = 10Log(10). For non ratios you tack on units, such as 30 dBHz = 10 Log(1 kHz). It just a way of expressing large values in engineering, and you can add the dB instead of multiplying in linear domain. You begin to think in dB after doing it for years.
The path losses stated in the replies are good examples when the rule is broken. The path loss is 22 dB + 20*Log(distance/wavelength). My universe/quark is just a joke of the most extreme ratio I can think of; I’m sure there are others larger.
It is an intelligence community convention to write codewords in ALL CAPS to differentiate them from the normal use of the same word. This doesn't indicate that they are acronyms. The appearance, though, combined with the fact that they are often in mixed use with acronyms, leads to a tendency for people to make up expansions of codewords which aren't intended to have one. Codewords were intentionally selected to have little if any relationship to what they describe.
To further muddy the waters, the military is just as fond of writing things in all caps as the intelligence community is, but they usually actually are acronyms or abbreviations. In contrast to TEMPEST consider PAVE PAWS, which is an acronym, and USSPACOM, which is abbreviation.
Replying with a burner account: TEMPEST is and has always been a code name, not an acronym. I've been seeing forced acronyms to TEMPEST for decades, all of them wrong because there is no acronym.
> [The characters'] goal is to facilitate anonymous Internet banking using electronic money and (later) digital gold currency, with a long-term objective to distribute Holocaust Education and Avoidance Pod (HEAP) media for instructing genocide-target populations on defensive warfare.
I would recommend it too. It's also one of few Neal Stephenson books in which the ending isn't completely missing or feels too phoned in (beware it IS somewhat unsatisfactory if you wanted more closure). The author unfortunately has a longstanding position where he "doesn't owe the reader a specific type of ending" and the real world doesn't provide textbooks ending either, if I remember correctly.
Such a shame because his books are on average excellent until the last 10-20%.
I do not! I liked the book, I find parts of it memorable, but I never recommend it as an introduction to Neal Stephenson. Unfortunately, Anathema is also a difficult book to recommend as an introduction.
> GNU Radio [2] is a Free & Open-Source Toolkit for Software Radio
[1] https://en.wikipedia.org/wiki/Tempest_(codename) [2] https://gnuradio.org