> What does "systemctl list-sockets" show?  Any services that systemd is
> providing a listener for should be listed here.

If you do spot a network socket service in that listing, you can stop the
current service with "systemctl stop blah.socket", and disable it in the
future (next reboot or VM restart) with "systemctl disable blah.socket".

There's always the potential that it could be re-enabled in the future by
installing another package dependent upon that service.  (That's bitten me
a couple of times.)

To block that from potentially happening, use "systemctl mask blah.socket"
and the service will stay off regardless of new dependencies.

("systemctl unmask" undoes the blocking.  Go figure.)

Oh yeah, to have those commands truly "stick," you should run them from
the template, not the AppVM.

Slight digression (from JJ, no way?!?!?): There's a few config things like
this (e.g. /etc/fstab) that I really think should be (by default) symlinks
to /rw/config, so they could be tweaked on an per-appVM basis.  (At risk
of a compromised VM being able to have more lasting hack-related effects
after a restart.)

It's easy enough to do in the template/appvm yourself, of course. e.g.:

# cp /etc/fstab /rw/config/fstab && ln -s /rw/config/fstab /etc/fstab

in the TemplateVM.  You could similarly do that with any systemctl config
files that you need different on a per-appVM basis.



You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to