All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Error when attempting to perform TLS NBD connection
Date: Wed, 6 Apr 2016 10:27:26 +0100	[thread overview]
Message-ID: <20160406092726.GD23124@redhat.com> (raw)
In-Reply-To: <4E8A67C7-A7C6-4F33-8CC3-FE1DCD2A0A31@alex.org.uk>

On Wed, Apr 06, 2016 at 10:22:45AM +0100, Alex Bligh wrote:
> 
> On 6 Apr 2016, at 10:11, Daniel P. Berrange <berrange@redhat.com> wrote:
> 
> > Oh I'd be interested to know if the unit tests pass for you - can you
> > run this
> > 
> >  make ./tests/test-crypto-tlssession ./tests/test-crypto-tlscredsx509
> >  ./tests/test-crypto-tlscredsx509
> >  ./tests/test-crypto-tlssession
> 
> See below. They pass.
> 
> I suppose the only other slightly non-standard thing I'm doing is
> running qemu-img as "./qemu-img" without installing it, as I already
> have Ubuntu's default qemu package installed. This used to work fine
> and it doesn't seem to linked to any 'old qemu' libraries (and besides
> 'old qemu' had no TLS code). I've put the output of ldd -v below
> as well just in case.

Running without installing certainly works fine - that's how I test
stuff on a daily basis.  Also there should be no fundamental reason
why this cannot work on gnutls 2.x - the original code I derived
everything from work with 2.x and even 1.x. So just need to chase
down the bug...

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2016-04-06  9:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 20:01 [Qemu-devel] Error when attempting to perform TLS NBD connection Alex Bligh
2016-04-06  9:09 ` Daniel P. Berrange
2016-04-06  9:11   ` Daniel P. Berrange
2016-04-06  9:22     ` Alex Bligh
2016-04-06  9:27       ` Daniel P. Berrange [this message]
2016-04-06  9:17   ` Alex Bligh
2016-04-06 11:13 ` Daniel P. Berrange
2016-04-06 11:40   ` Alex Bligh
2016-04-06 12:18     ` Daniel P. Berrange

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160406092726.GD23124@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex@alex.org.uk \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.