libvirt/src/locking/virtlockd-admin.socket.in

[Unit]
Description=Virtual machine lock manager admin socket
Before=libvirtd.service

[Socket]
ListenStream=@localstatedir@/run/libvirt/virtlockd-admin-sock
Service=virtlockd.service
SocketMode=0600

[Install]
WantedBy=sockets.target
lockd: add support for admin protocol in virtlockd Add a virtlockd-admin-sock can serves the admin protocol for the virtlockd daemon and define a virtlockd:///{system,session} URI scheme for connecting to it. Signed-off-by: Daniel P. Berrange <berrange@redhat.com> 2018-01-19 14:54:00 +00:00			`[Unit]`
			`Description=Virtual machine lock manager admin socket`
			`Before=libvirtd.service`

			`[Socket]`
			`ListenStream=@localstatedir@/run/libvirt/virtlockd-admin-sock`
lockd: fix typo in virtlockd-admin.socket Commit ce7ae55ea1 introduced a typo in virtlockd-admin socket file /usr/lib/systemd/system/virtlockd-admin.socket:7: Unknown lvalue 'Server' in section 'Socket' Change 'Server' to 'Service'. Signed-off-by: Jim Fehlig <jfehlig@suse.com> Reviewed-by: Erik Skultety <eskultet@redhat.com> 2018-03-14 22:42:39 +00:00			`Service=virtlockd.service`
locking: restrict sockets to mode 0600 The virtlockd daemon's only intended client is the libvirtd daemon. As such it should never allow clients from other user accounts to connect. The code already enforces this and drops clients from other UIDs, but we can get earlier (and thus stronger) protection against DoS by setting the socket permissions to 0600 Fixes CVE-2019-10132 Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> 2019-04-30 15:51:37 +00:00			`SocketMode=0600`
lockd: add support for admin protocol in virtlockd Add a virtlockd-admin-sock can serves the admin protocol for the virtlockd daemon and define a virtlockd:///{system,session} URI scheme for connecting to it. Signed-off-by: Daniel P. Berrange <berrange@redhat.com> 2018-01-19 14:54:00 +00:00
			`[Install]`
			`WantedBy=sockets.target`