Here is the source JPL article:
https://www.jpl.nasa.gov/news/news.php?feature=7339
Curiosity rover gives Nasa a scare, needed a reset
21–27 of 27 posts
Re: Curiosity rover gives Nasa a scare, needed a reset
#22So how cautious are you when debugging a valuable system like this? I imagine you’re not allowed to just ssh and `sudo -u less logs`
Debugging a system like this must very scary because of the tremendous responsibility. It is intersting to know how they actually communicate with it and handle auth.
Re: Curiosity rover gives Nasa a scare, needed a reset
#23So how cautious are you when debugging a valuable system like this? I imagine you’re not allowed to just ssh and `sudo -u less logs`
Debugging a system like this must very scary because of the tremendous responsibility. It is intersting to know how they actually communicate with it and handle auth.
It might not be authenticated. For some NASA probes, they just figured that any attacker would need control of a global network of high-gain radio antennas, and there aren't very many of those. Physical security at DSN tracking sites is sufficient in most cases.
Re: Curiosity rover gives Nasa a scare, needed a reset
#24Earlier quoted context omitted.
Debugging a system like this must very scary because of the tremendous responsibility. It is intersting to know how they actually communicate with it and handle auth.
It might not be authenticated. For some NASA probes, they just figured that any attacker would need control of a global network of high-gain radio antennas, and there aren't very many of those. Physical security at DSN tracking sites is sufficient in most cases.
I wonder if this threat vector will change as more countries become space bound. Curious to see the JPL Security Coding Guidelines, whenever that is written.
Re: Curiosity rover gives Nasa a scare, needed a reset
#25Just restart the Docker container. Amateurs!
Re: Curiosity rover gives Nasa a scare, needed a reset
#26Where can I read about how Curiousity’s hardware and software works at a low level so things like communications still work in safe mode? Truly fascinating engineering.
Re: Curiosity rover gives Nasa a scare, needed a reset
#27Earlier quoted context omitted.
It might not be authenticated. For some NASA probes, they just figured that any attacker would need control of a global network of high-gain radio antennas, and there aren't very many of those. Physical security at DSN tracking sites is sufficient in most cases.
I wonder if this threat vector will change as more countries become space bound. Curious to see the JPL Security Coding Guidelines, whenever that is written.
AES-256 on both uplink and downlink sides. It's fast enough and the NSA thinks it's good enough. Put a timestamp inside the cleartext to prevent replay attacks and re-key the encryption module every so often to prevent cryptoanalysis from breaking your current key.