Skip to content

Comment on NASA knows what knocked Voyager 1 offline, but it will take a while to fixparent

Comments

Does it use 1970s encryption?

That would actually be fine, because you can do encryption in software. So you wouldn't need to keep any physical artifacts from the 1970s around.

I think OP's concern was more around that it's likely easy to break any encryption that was used in the 1970s so someone could send the spacecraft malicious commands.

That said, only America, China, Europe, India, Japan and Russia have deep space networks and none of them have anything to gain from investing the resources into trying to harm Voyager. Even with weak encryption it's likely difficult to collect enough samples to be able to break it and even once it's broken you still need to figure out a valid set of commands to send to achive your goal.

it's likely easy to break any encryption that was used in the 1970s

I wouldn't jump to that conclusion. Some things encrypted now are intended to be secure for 50 years.

We have much better chances of designing a cryptography system today that can survive 50 years of math, and with computers a billion times faster we can make the encryption O((1.something)^billion) times harder to brute force. Nothing in the 70s was capable of resisting today's attacks.

You mention a one-time pad in another comment. In theory they could have sacrificed a bunch of tape space to store a pad for commands.

Encryption in the 70s resists today's attacks just fine. DES was weakened on purpose (short key length, but the idea for 3DES dates from 1978). In the asymmetric realm you still can't break a full length RSA key.

Maybe it's not fully contemporaneous with Voyager but the claim that 70s encryption is insufficient doesn't stand up to scrutiny

It's not the full length RSA key that's the worry, though, it's the structure around it that Bleichenbacher finds clever ways of poking holes in.

I don't think Voyager would be very vulnerable to an adaptive chosen ciphertext attack regardless. But you don't need the 70s maths to be wrong, you only need the engineering to have a flaw.

Is today's engineering different? One could argue that we have 50 years more of experience with the engineering (though the components have changed too, requiring newish engineering), and I would guess that we invest more resources in such things these days.

What was "full length" at the time, even if they got RSA implemented immediately after the paper was announced?

The RSA paper recommends 200 digit keys, which is somewhat under 700 bits. Would even that size run acceptably on an 8 kiloword 0.1MIPS machine? (I couldn't quickly find an actual opcode listing, so I can't say exactly how fast it multiplies, but it's probably not great.)

Why would you use public key encryption here in the first place? Just use a symmetric cipher.

What's a symmetric cipher from the 70s that we can't brute force today?

(And I'm not counting "the idea" of 3DES when even that was after voyager already launched and it wasn't properly set up until 1981. Also 3DES has enough weaknesses that I wouldn't trust it to be uncrackable today.)

Theoretically but probably not practically.

It’s doubtful that there’s enough processing or memory headroom for any decent encryption.

You’d have to not only add decryption routines, a key (even 128 bits is a lot!), and that’s another point of failure.

As we know one of the memory modules already corrupted, so if encryption was implemented, chances are the Voyager would be a brick now.

It’s doubtful that there’s enough processing or memory headroom for any decent encryption.

Maybe they use a one-time pad. :) I'm only half joking (imagining the person who has spent the last 40+ years on Voyager with a book). Why not? How much memory and cpu would be required?

OP might be concerned it's bogus untested crypto from the bleeding edge 70s. not tested crypto from the 40s to 60s we use safely on everything today.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.