Every managed service was going through the motions of creating a
rhizome user, and then not using it, instead installing into
/home/ubi, which is our default non-root, sudo-capable virtual machine
user.
This is bad for management of `authorized_keys` between machine and
personnel login, a future auditing system (separating administrative
and automated activity), it's bad for parity (on VmHosts, the concerns
were split as designed between `root` [which is bad for other reasons]
and rhizome, and finally, it renders 22f3aa5c, which will terminate
sessions from abandoned connections in a timely manner, but only does
so for the user name `rhizome` (via the configuration
`KillOnlyUsers=rhizome`)
1b54d1b87a