libvirt/src/locking
Daniel P. Berrangé f111e09468 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-05-21 13:05:00 +01:00
..
domain_lock.c
domain_lock.h
libvirt_lockd.aug
libvirt_sanlock.aug
lock_daemon_config.c Revert "Include unistd.h directly by files using it" 2019-04-10 12:26:32 +02:00
lock_daemon_config.h
lock_daemon_dispatch.c
lock_daemon_dispatch.h
lock_daemon.c Always put _LAST enums on second line of VIR_ENUM_IMPL 2019-04-11 12:47:23 -04:00
lock_daemon.h
lock_driver_lockd.c Revert "Include unistd.h directly by files using it" 2019-04-10 12:26:32 +02:00
lock_driver_lockd.h
lock_driver_nop.c
lock_driver_nop.h
lock_driver_sanlock.c
lock_driver.h
lock_manager.c
lock_manager.h
lock_protocol.x
lockd.conf
Makefile.inc.am src: don't statically link code that's already in libvirt.so 2019-05-17 14:34:45 +01:00
sanlock_helper.c
sanlock.conf
test_libvirt_lockd.aug.in
test_libvirt_sanlock.aug.in
test_virtlockd.aug.in
virtlockd-admin.socket.in locking: restrict sockets to mode 0600 2019-05-21 13:05:00 +01:00
virtlockd.aug
virtlockd.conf
virtlockd.pod
virtlockd.service.in
virtlockd.socket.in locking: restrict sockets to mode 0600 2019-05-21 13:05:00 +01:00
virtlockd.sysconf