DMcCunney wrote:]And precisely who would do that hacking?
Effecting hacking requires both a high level of skill and known vulnerabilities in the target system. Most of the hacking and identity theft we hear about relies on user stupidity, like all the probably phishing messages Gmail intercepts here.
You can assume Federation level tech had largely passed beyond humans writing code. I'd expect a lot of code to be generated by AIs, in part to have code that didn't have vulnerabilities.
(I've been a systems, network, and telecom admin, and follow various development efforts. I see both whole new languages designed to avoid the sort of vulnerabilities inherent in coding in C, like Go and Rust, and an increasing emphasis on "Design for Test", where new commits to a repository must include tests that demonstrate the code behaves as specified and doesn't choke on the data it manipulates.
Current practice starts with "never trust your data!" An awful lot of vulnerabilities being patched back when covered cases like a program allocating a buffer of X KB to hold data, and being fed more. What happens to the more?
Previously, it overflowed into some other part of memory and possibly overwrote critical code. It simply didn't occur to the developers who wrote that code that someone might do that deliberately and they didn't check for it.)
You can also assume something more than a simple password to confirm the identity of the person given access. I'd bet on some sort of biometrics like fingerprints and retinal scans but more sophisticated.
I don't see hacking as a viable explanation. (And from TextEv, the angel I see being able to do it was Dr. Proctor, who hacked Nimue's PICA software to get past the 10 day activation limit. I don't see a lot of other folks with that level of skill existing on Safehold.)
______
Dennis
Hacking might be the wrong word. Better terms might be "edit wars" "Credentials Battle" or "Physical Access Fight".
hypotheticaly, it might look something like this...
Langhorne has full admin rights to the AI that controls the bombardment system, and said AI mainframe is stored inside his HQ.
Kau-Yung nukes the HQ, killing both Langhorne and the AI.
The simpler, local, emergency backup bombardment system AI reverts to local control, with a list of pre-approved losers, verified by their NEATS. Chiriro is at the top of the list, with LIMITED admin rights. Chiriro revokes the access priviliges for everyone with lower-ranking credentials than his, including Schueler.
Schueler, however, has senior admin priviliges over the COMM SYSTEMS, and in order for Chiriro's NEAT to communicate with a backup computer in high Safehold Orbit, the messages have to go through Schueler's comm systems. Schueler revokes everyone's right to use the comm system for orbital-range communications, therefore, neither Chiriro nor anyone else can easily send a message out to the bombardment satelites in the first place. No message transmission means no orders.
Chiriro hot-wires several of the groundside communications dishes using physical access, forces them to undergo a hard reboot to factory default settings, then orders the reset radio dishes to treat Chiriro as the primary admin from now on.
Schueler makes a secret personality backup, then attempts to perform lead-pipe cryptography on Chiriro's knees...
Chiriro kills Schueler, then convinces all AI networks under Schueler's former command that since Chiriro hasn't been convicted of murder, Chiriro must inherit all of Schueler's legal authority over comms systems, per the established legal chain of command.
Schueler's VR persona wait till Chiriro dies of old age, then awakens and re-claims command of the comm systems...
Obviously, that's a purely hypothetical scenario, and didn't really occur that way... but I suspect that's the sort of thing most people are thinking of when they propose a "hacking" war between angels, even though that isn't technically computer hacking in the way we normally think of it.