i am working on a thing.
Specific problem now, long story short: I want to automatically create onion vanity addresses. For this i have a separate qube, that i don’t want to have.
To solve this without the extra qube on standby i would love to create it on demand from a domU.
Also for other projects of mine that feature would be very awesome. Something like a management qube that starts the stuff i want done in other qubes. What i want is an management qube.
The management domU:
No network obviously. My shell, my everything i want it to have (compared to dom0). Should manage my qubes, Autostarts the stuff i want autostarted in the way i want it autostarted. (that way my config stuff could be in one place for ease of use. At least i hope). Usability features like being able to copy stuff into it from the clipboard.
Capabilities the management VM should have:
- Create new qubes
- Modify qubes preferences (CPU cores, network-vm, …)
- Start qubes
- Run (predefined) programs in the qubes via qrexec
- (Maybe even mount block devices into qubes to specific places, not sure about that tho)
Why not control stuff from dom0?
Usability. I need to give arguments to the stuff i am calling. Long arguments like 50 character passwords in extreme cases that i will not type into dom0.
Security: Don’t put more software that could explode into dom0.
Availability: I know i will fuck up at one time tinkering. I don’t want to fuck up in dom0 if possible.
So far i think the worst that could happen would be a DOS of the system (if implemented securely, so the “management” qube cannot gain RCE in dom0).
What do you think? How bad of an idea is that?
: Other stuff i want to do from my management qube:
- archiveBox qube: Issue a command to archive a website
- download qube: Issue a command to download something of the internet and safe it in an storage qube
- server management: ssh into all my machines and do “stuff”
- On demand services: like “Give me a dispVM with a running drawio docker running and sync all i did afterwards with my storage”
All of the above in dispVMs that