Unless the military upgrades their signal to some sort of broadband, frequency-hopping, encrypted stuff, this WILL happen again.
Also there's the simple matter that GUIs work better for unfamiliar situations. While it might be easy to just say "Well a good admin should know about this," that is rather stupid. Nobody knows everything, you never get someone with limitless experience. Part of systems administration is being able to solve novel problems.
Documentation should exist. And should cover those unfamiliar situations.
Ergo any good admin should be an habitué at manual reading, then he/she would be able to solve any unfamiliar examples.
Or, how the heck should one work on a remote server over a 500ms ping-time satellite connection??? Remote desktop?
First, if an agency is encrypting their communications, there's not much hope for any other service to talk to them, unless (obviously), they all share keys. It's doubtful, though, that the FBI is going to share their encryption keys with the local volunteer fire department. So, the assumption must be made that this solution is meant for unencrypted (which is not to say, unencoded digital) communications.
just set the primary channel to use $AGENCY key while secondary (and other channels) to use $OTHER_AGENCY key. Duh.
Then, just make it SOP to transmit on primary while on $AGENCY bussiness and secondary while on cooperative work.
Rocks may not have DNA
Not DNA per se, but each have their own mineral (or chemical, or magnetic) signature that allows one to tell its lineage, and even predict how it's going to "evolve".
Just ask a geologist.
BTW, Geology Rocks.
The absence of labels [in ECL] is probably a good thing. -- T. Cheatham