similar to: [libnbd PATCH] interop: Don't fail qemu tls testing if nbdkit was not installed

I was a little surprised to find that LIBNBD_TLS_ALLOW worked out of the box, so I had to examine the logs whereupon I saw the magic message ... libnbd: debug: nbd1: nbd_connect_command: server refused TLS (policy), continuing with unencrypted connection I don't believe this path has ever been tested before. It's possible the tests could be improved if they actually checked for this

Now that we have implemented systemd socket activation, we can use this to run qemu-nbd in tests. The first patch leaves some dead code around (the -DSERVE_OVER_TCP=1 path). It's possible we might want to use this to test against a putative future NBD server that only supports TCP, but on the other hand maybe we should just remove it. Tests & valgrind still pass for me. Rich.

Test both the TLS enabled and fallback paths. nbd-server doesn't appear to support TLS at all, and qemu-nbd is known not to allow fallback to unencrypted, and therefore it only makes sense to test nbdkit at the moment. --- .gitignore | 4 ++++ TODO | 3 --- interop/Makefile.am | 54 +++++++++++++++++++++++++++++++++++++++++++++ interop/interop.c | 30

This borrows from a trick in libvirt - by defining $(NULL) to expand to an empty string, we can more consistently write multi-line macros where all useful lines terminate with \, making it easier to add/remove lines without worrying about whether \ needs to be touched up on neighboring lines. --- Looks big, but is fairly mechanical. I'm also doing a similar patch for nbdkit, where it would

This commit adds a simple test of qemu-storage-daemon (QSD). On the basis that QSD is just qemu-nbd in new clothes this is only a simple test, not complete coverage. Nor does it test the unique features of QSD like being able to use QMP to create new server instances. Unfortunately QSD is not yet stable upstream. This version works with qemu 5.1.0 but at least two of the command line

We're setting up a connection with Level3's voip system and when we use Asterisk or make or recv calls we get an initial pulsing noise. Level3's Interop team explains that's their RTP extension headers and Asterisk apparently doesn't know what to do with it. He said we need to either ignore or of course let the traffic pass. Has anyone heard of this before? I understand the

Dear all, I have a SUN server running as ClearCase view-server and am using Samba for Interop. Today I updated Samba from 3.0.21c to 3.0.24 and now I cannot mount/start my views from windows!! MVFS error log on my windows client gives "{8 pid/tid 49800000c58/85fdf178} MvfsFsNotification: Unsupported filesystem type (6)" Samba logs don't show any error... Trying other

Has anyone done interop testing with Level 3 and Asterisk. If so, would you be willing to share your experiences. Gene -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050308/061aea35/attachment.htm

Does anybody know how big a presence Asterisk and/or Digium will make at Networld Interop this year? I have a part-time guy that is building an Asterisk system for us (in a proof of concept fashion before we do a full switch to it) that I would like to take, but I don't want to waste his time if it is going to just be a "yeah, try our product" booth and not something he

On 9/17/19 5:35 PM, Richard W.M. Jones wrote: > Test both the TLS enabled and fallback paths. > > nbd-server doesn't appear to support TLS at all, and qemu-nbd is known > not to allow fallback to unencrypted, and therefore it only makes > sense to test nbdkit at the moment. > --- > .gitignore | 4 ++++ > +interop_nbdkit_tls_certs_allow_enabled_SOURCES =

This neutral refactoring adds -DTLS_MODE. We can in future change the requested TLS mode, but not in this commit. It also checks that nbd_get_tls_negotiated returns true after connecting, when the requested mode was set to LIBNBD_TLS_REQUIRE. --- interop/Makefile.am | 4 ++++ interop/interop.c | 26 ++++++++++++++++++++------ 2 files changed, 24 insertions(+), 6 deletions(-) diff --git

The test interop-qemu-nbd-tls-certs frequently fails on slow (32 bit) machines in Fedora Koji. (Is crypto slow on these already overloaded machines?) As we cannot wait for a signal when qemu-nbd is ready start serving, we have to use a sleep. The current sleep is 5 seconds, which is not long enough. Making the sleep longer would work but is inconsiderate for people using faster machines.

https://bugzilla.mindrot.org/show_bug.cgi?id=2639 Bug ID: 2639 Summary: PuTTY interop tests broken Product: Portable OpenSSH Version: 7.3p1 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: Regression tests Assignee: unassigned-bugs at mindrot.org

On 9/17/19 5:35 PM, Richard W.M. Jones wrote: > This neutral refactoring adds -DTLS_MODE. We can in future change the > requested TLS mode, but not in this commit. > > It also checks that nbd_get_tls_negotiated returns true after > connecting, when the requested mode was set to LIBNBD_TLS_REQUIRE. > --- > interop/Makefile.am | 4 ++++ > interop/interop.c | 26

Hi, Can anyone tell me where I can get sample C# code to call the native (win32) dll vorbisfile.dll to decode a vorbis Stream? I want the native performance of this methodology, however Ive tried porting the invocation code to C# and keep getting null reference errors when Calling ov_open_callback. Thanks - Adam -------------- next part -------------- An HTML attachment was

This is slightly redundant with just trying nbd_set_tls(nbd, 2) then checking for failure; however, this function does not set errors and looks more similar to nbd_supports_uri. --- This is borderline enough that I figured I'd post it to check if we want it. generator/generator | 45 ++++++++++++++++++++++++++++++++++++++------- interop/interop.c | 4 ++++ lib/handle.c | 12

This adds new APIs for running a local NBD server and connecting to it using systemd socket activation (instead of stdin/stdout). This includes interop tests against nbdkit and qemu-nbd which I believe are the only NBD servers supporting socket activation. (If we find others then we can add more interop tests in future.) The upstream spec for systemd socket activation is here:

Hi, I have read lots of confusing and even contrary statements as to how to configure a Samba share which may also be accessed via NFS. >From one thread [1] on the samba-technical list I gather that disabling kernel oplocks will be enough. So my questions are: Will turning off kernel oplocks be enough to ensure safety while also exporting the same share with NFS? Do I need to consider any

I'm looking for some software to do emulation of phones so that I can test out a whole range of phones and their firmware revisions against asterisk. Anyone know of something like that? I'm hoping that the hardware vendors have something like that, and _maybe_ I'm really lucky and they are using something somewhat standard like qemu. Cheers, spd -- | It ain't what you

This adds new APIs for running a local NBD server and connecting to it using systemd socket activation (instead of stdin/stdout). This includes interop tests against nbdkit and qemu-nbd which I believe are the only NBD servers supporting socket activation. (If we find others then we can add more interop tests in future.) The upstream spec for systemd socket activation is here: