The tool for testing SASL-Authentication "testsaslauthd" uses sockets:
strace:
socket(PF_FILE, SOCK_STREAM, 0) = 3
connect(3, {sa_family=AF_FILE, path="/var/run/saslauthd/mux"}, 110) = 0
writev(3, [{"\0\4root\0\4root\0\4imap\0\0", 20}], 1) = 20
read(3, "\0\2", 2) = 2
On Fri, Jan 20, 2012 at 12:55:09AM +0100, Robyn Bachofer wrote:
> Hi list,
>
> I've been thinking and I think the right question is:
> - about which is libvirt access to sasl, socket?
> - which is transmitted?
> and
> - what is expected libvirt?
>
> (e.g. shadow have no service/application assign
Hi list,
I've been thinking and I think the right question is:
- about which is libvirt access to sasl, socket?
- which is transmitted?
and
- what is expected libvirt?
(e.g. shadow have no service/application assignment)
:) regards
Robyn
2012/1/18 Robyn Bachofer
> Hi list,
>
> i have a p
Hi list,
i have a problem with virt-manager authentication over tcp.
I tried it with virt-manager over non-TLS "TCP (SASL/Kerberos)" auth. and
the sasl mechanism "shadow".
The user (tested with unprivileged user and root) is allready in the group
libvirt(d) and the process is running as root.
T
