4 ms·
The way I'd in principle want to solve this problem (controlling access to root-level resources that don't support delegation) would be with some kind of "escor
by ameliaquining 3y ago
The way I'd in principle want to solve this problem (controlling access to root-level resources that don't support delegation) would be with some kind of "escorted remote access" system, wherein an authorized set of people can remotely log into a special browser session that's able to act as the root user, but only with another authorized party watching and monitoring the session and able to kill it, so that no one can act unilaterally. Unfortunately, I'm presently unaware of any off-the-shelf software that does this; I've been vaguely thinking about doing it as an open source side project.
- mfashby 3y agoI've been thinking of a similar project but over SSH rather than a browser based thing.
- ameliaquining 3y agoProblem with that is that not everything is controllable over ssh. Sometimes you have to use a web interface provided by a vendor because that's the only thing they offer.
- mfashby 3y agotrue, On the other hand I think a two-person SSH is probably an easier thing to build in terms of recording what was done for audit, and maybe even require both parties to confirm commands before executing them. Also your SSH server could require both parties with different keys to login before it starts or something. I think this kind of stuff would be harder to implement in a web browser (but just as useful probably)