> The better solution would probably be to add the cockpit user to the
libvirt group.
There is no cockpit user, this is normal user. I think we should connect
to both ` /var/run/libvirt/libvirt-sock` for system session and to
`$XDG_RUNTIME_DIR/libvirt/libvirt-sock` for user session.
However I am
The better solution would probably be to add the cockpit user to the
libvirt group.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891311
Title:
New version of libvirt-sock has wrong permissions
To
Hi Matej amd g3blv,
This unfortunately was a security issue - see [1]
If you explcitly want it to be open to everyone you'd want to add a drop in
config for the socket
$ systemctl edit libvirtd.socket
SocketMode=0666
Then you are back to how it was before, but unsecured as documented by
the CV
I faced the same issue and the suggested solution solved my issue. Would
be great though if the suggested solution wasn't needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891311
Title:
New ver
