On 7/5/19 4:31 AM, Max Reitz wrote: > On 04.07.19 00:47, Eric Blake wrote: >> Although you generally won't use encryption with a Unix socket (after >> all, everything is local, so why waste the CPU power), there are >> situations in testsuites where Unix sockets are much nicer than TCP >> sockets. Since nbdkit allows encryption over both types of sockets, >> it makes sense for qemu-nbd to do likewise. > > Hmm. The code is simple enough, so I don’t see a good reason not to. >
> Um, also, a perhaps stupid question: Why is there no passing test for > client authorization? > Not a stupid question. It's copy-and-paste from the existing test over TCP, which Dan added in b25e12daf without any additional successful test I guess the earlier tests in the file are the success cases, and this just checks that authz restrictions cover the expected failure case of something that would succeed without authz? Or maybe that commit really is incomplete? -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
