2. Based on commentary from native Persian speakers on this thread, it would appear that no one is claiming that the drone was remotely piloted by Iranians into US Airspace, but rather the one that was shot down in Iran several months ago (confirmed by the US Government) had these photos on it.
3. See above, there are at least 2 Persian speakers on this thread. HN is a LOT more diverse than you realize.
"2. Based on commentary from native Persian speakers on this thread, it would appear that no one is claiming that the drone was remotely piloted by Iranians into US Airspace, but rather the one that was shot down in Iran several months ago (confirmed by the US Government) had these photos on it."
If this is true it means the Iranians compromised the encryption on the UAV's drive, which would be seriously not good.
The Iranians outsmarting NSA encryption? Not likely. Possible in theory and a huge deal, but not likely. If they decrpyted something from a military aircraft, it's much more likely that shoddy engineering work was done on that aspect of said aircraft because it was decided that security wasn't a top concern. (And, indeed, having pictures of JFK _isn't_ a big deal.)
What exactly is "milspec"? I was under the impression that military security standards in the US _are_ produced by the NSA.
highly likely the Russians would help the Iranians in such an endeavor in exchange for intelligence sharing.
I must be missing something... yes, but what do Russians have to do with it? I thought this was a US drone captured by Iranians. Genuine question here.
MIL-SPEC means encryption built to military specifications. It includes, but does not equate to, NSA Suite B cryptography. As you can imagine, using crypto designed by a paranoid spook agency would not be appropriate for all military applications, for example a near-real-time flight application. As a result, there are a variety of encryption standards used by the military, some of which would be approved by the NSA, others which wouldn't.
It's a good question about the Russians. The ties between Russia and Iran are much tighter than most in the US realize, especially when it comes to national security, and particularly with regard to US-related issues. If we used industrial grade crypto on a system, it would be in line with past behaviors for the Russians to help the Iranians with it.
Regarding the Russians: Oh, I see, now. Yes, you're right that if country X cracks our encryption, we can't assume that they didn't get help from <insert China or Russia here>.
for example a near-real-time flight application.
Wait, why do you say such a system wouldn't use NSA-grade encryption?
Primarily latency. Now, ideally you'd like the entire subsystem moved off disk into volatile memory, but for some things you're going to have to read from disk. I can imagine cases where that wouldn't be easily feasible if the drive had NSA crypto.
"Regarding the Russians: Oh, I see, now. Yes, you're right that if country X cracks our encryption, we can't assume that they didn't get help from <insert China or Russia here>."
Right, but its more than that in the case of the Iranians. The Russians have a long and documented history of assistance to the Iranians and the Syrians.
for some things you're going to have to read from disk.
I'm not sure I follow. For some things you're going to have to _write_ to disk... like captured video. (I wouldn't consider that to be the "real-time" part of the software, though.) And you might have to read from disk occasionally... maybe you have map information stored there... but that probably doesn't need to be real-time. Can you tell me an example where you would need to read from disk in real-time? (Which I think should anyway be impossible, regardless of whether or not heavy crypto is being used.)
The Russians have a long and documented history of assistance to the Iranians and the Syrians.
Sure! Man I love when people on hn ask genuine questions rather than trying to one up one another. It's one of the reasons I was so reluctant to stop lurking for so long.
Much like the Mars rovers, the navigation system is loaded in a modular fashion, with complex algorithms for each scenario loaded on the fly. So for example, imagine a UAV goes into a stall. Likely the aircraft needs a whole new set of algorithms to recover. It's very likely I this case you'd need low latency disk reads. Now again, this is just a guess based upon my experience with similar systems. I've never developed a UAV system.
Man I love when people on hn ask genuine questions rather than trying to one up one another. It's one of the reasons I was so reluctant to stop lurking for so long.
Well then, you're exactly the kind of person we need to stop lurking and start participating, so welcome aboard. But yeah, I totally understand you.
this is just a guess based upon my experience with similar systems
You mean planetary rovers? If not, can you be more specific? I realize it's not necessarily wise to divulge too much industrial information. I actually have worked on UAVs... not to the point that I can say the scenario you're presenting is incorrect (I wasn't involved in that kind of stuff), but I don't think it's very plausible. I could see that strategy being more reasonable on a super memory-constrained device where the system is radiation hardened, like space equipment. I would think for a normal UAV, you'd just keep all the code (algorithms) you might need in memory.
Its possible I'm wrong. I've never designed a UAV flight system, so I was speculating as to reasons why a lower level of encryption might be needed. Its possible that's not a realistic constraint for atmospheric craft.
Comments
1. You have a lot more confidence in our government's ability to accurately compile lists than I do, particularly in light of the failures of the no-fly list: https://en.wikipedia.org/wiki/No_Fly_List#False_positives
2. Based on commentary from native Persian speakers on this thread, it would appear that no one is claiming that the drone was remotely piloted by Iranians into US Airspace, but rather the one that was shot down in Iran several months ago (confirmed by the US Government) had these photos on it.
3. See above, there are at least 2 Persian speakers on this thread. HN is a LOT more diverse than you realize.
https://en.wikipedia.org/wiki/Iran–U.S._RQ-170_incident
"2. Based on commentary from native Persian speakers on this thread, it would appear that no one is claiming that the drone was remotely piloted by Iranians into US Airspace, but rather the one that was shot down in Iran several months ago (confirmed by the US Government) had these photos on it."
If this is true it means the Iranians compromised the encryption on the UAV's drive, which would be seriously not good.
The Iranians outsmarting NSA encryption? Not likely. Possible in theory and a huge deal, but not likely. If they decrpyted something from a military aircraft, it's much more likely that shoddy engineering work was done on that aspect of said aircraft because it was decided that security wasn't a top concern. (And, indeed, having pictures of JFK _isn't_ a big deal.)
Totally possible the imaging equipment retains data in an insecure fashion.
However, milspec != NSA, and its highly likely the Russians would help the Iranians in such an endeavor in exchange for intelligence sharing.
What exactly is "milspec"? I was under the impression that military security standards in the US _are_ produced by the NSA.
I must be missing something... yes, but what do Russians have to do with it? I thought this was a US drone captured by Iranians. Genuine question here.
MIL-SPEC means encryption built to military specifications. It includes, but does not equate to, NSA Suite B cryptography. As you can imagine, using crypto designed by a paranoid spook agency would not be appropriate for all military applications, for example a near-real-time flight application. As a result, there are a variety of encryption standards used by the military, some of which would be approved by the NSA, others which wouldn't.
It's a good question about the Russians. The ties between Russia and Iran are much tighter than most in the US realize, especially when it comes to national security, and particularly with regard to US-related issues. If we used industrial grade crypto on a system, it would be in line with past behaviors for the Russians to help the Iranians with it.
Thanks.
Regarding the Russians: Oh, I see, now. Yes, you're right that if country X cracks our encryption, we can't assume that they didn't get help from <insert China or Russia here>.
Wait, why do you say such a system wouldn't use NSA-grade encryption?
Primarily latency. Now, ideally you'd like the entire subsystem moved off disk into volatile memory, but for some things you're going to have to read from disk. I can imagine cases where that wouldn't be easily feasible if the drive had NSA crypto.
"Regarding the Russians: Oh, I see, now. Yes, you're right that if country X cracks our encryption, we can't assume that they didn't get help from <insert China or Russia here>."
Right, but its more than that in the case of the Iranians. The Russians have a long and documented history of assistance to the Iranians and the Syrians.
I'm not sure I follow. For some things you're going to have to _write_ to disk... like captured video. (I wouldn't consider that to be the "real-time" part of the software, though.) And you might have to read from disk occasionally... maybe you have map information stored there... but that probably doesn't need to be real-time. Can you tell me an example where you would need to read from disk in real-time? (Which I think should anyway be impossible, regardless of whether or not heavy crypto is being used.)
Yeah, very true, I have noticed that, too.
Sure! Man I love when people on hn ask genuine questions rather than trying to one up one another. It's one of the reasons I was so reluctant to stop lurking for so long.
Much like the Mars rovers, the navigation system is loaded in a modular fashion, with complex algorithms for each scenario loaded on the fly. So for example, imagine a UAV goes into a stall. Likely the aircraft needs a whole new set of algorithms to recover. It's very likely I this case you'd need low latency disk reads. Now again, this is just a guess based upon my experience with similar systems. I've never developed a UAV system.
Well then, you're exactly the kind of person we need to stop lurking and start participating, so welcome aboard. But yeah, I totally understand you.
You mean planetary rovers? If not, can you be more specific? I realize it's not necessarily wise to divulge too much industrial information. I actually have worked on UAVs... not to the point that I can say the scenario you're presenting is incorrect (I wasn't involved in that kind of stuff), but I don't think it's very plausible. I could see that strategy being more reasonable on a super memory-constrained device where the system is radiation hardened, like space equipment. I would think for a normal UAV, you'd just keep all the code (algorithms) you might need in memory.
Its possible I'm wrong. I've never designed a UAV flight system, so I was speculating as to reasons why a lower level of encryption might be needed. Its possible that's not a realistic constraint for atmospheric craft.