There is a back door to everything operating on software, everything. Just ask the Iranians, or better yet, the White House. In the event you missed it, reread my post and the position I held from 74-76. It was much tougher to “crack” the code back then because the availability of the computers necessary to do so was extremely limited.
So I guess you can sleep comfortably thinking that just because it was a “controlled” exercise that someone with the access to technology way above UTA is not going to work on it because it was monitored by DHS. It is far different to expect an event than it is to it happening as a total surprise.
Iranians had nothing to do with that UAV incident. Nothing. At. All. You wish to believe a third world nation has the expertise to lock-up flight controls then have at it.
Better computers today doesn’t mean easier to crack code as the computers today are better when it comes to writing code and protecting software.
“In the event you missed it, reread my post and the position I held from 74-76.”
I suppose you can sleep comfortably feeling that you are well aware of up-to-date UAV/RPV technology because of what you did nearly 40-yrs ago. (By the way, you are not the only one with experience behind the “Black” door).
“It is far different to expect an event than it is to it happening as a total surprise.”
Executive lead agent for UAV/RPV development is USAF, not DHS. DHS does their own R&D, limited as it is, to modify for their own missions. They are not aware of DOD UAV/RPV state-of-the-art technology/protections.
Of course, based upon your two years of experience nearly 40-yrs ago, you are fully aware we “hack at” everything all the time, exploring for weaknesses and flaws, to find where things can/need to be improved. This is the smart thing to do because as you are also aware, “There are no bug-free programs, just undiscovered bugs.”