qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Patch 3/4] [RFC]  Zero Cluster Dedup, Offline dedup, qemu-img extentions
Date: Mon, 6 Oct 2008 18:46:06 +0100	[thread overview]
Message-ID: <20081006174606.GW20979@redhat.com> (raw)
In-Reply-To: <ED2414DB5FBBCF4FA66ECE71F290E9A2C942D1@EXVBE011-2.exch011.intermedia.net>

On Mon, Oct 06, 2008 at 10:31:39AM -0700, Shahar Frank wrote:
> MDSUM Extension for the map verb
> 
> Signed-off-by: Shahar Frank <shaharf@qumranet.com>
> 
> @@ -496,6 +501,7 @@ elif [ "$bsd" = "yes" ]; then
>  else
>      # Some Linux architectures (e.g. s390) don't imply -lpthread
> automatically.
>      AIOLIBS="-lrt -lpthread"
> +    MD5SUMLIBS="-lssl"
>  fi
>  
>  # Check for gcc4, error if pre-gcc4
> @@ -920,6 +926,20 @@ EOF

We're already linking to GCrypt/GNUTLS for SSL stuff in the VNC server, and
one crypto/SSL library per application really ought to be enough. GCrypt
has APIs for doing md5 hashing (and pretty much every other hashing algo
you can think of). Furthermore, OpenSSL's licensing terms are commonly 
considered to be incompatible with the GPL, unless you add an explicit
exception allowing linking to OpenSSL.

Regards,
Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  reply	other threads:[~2008-10-06 17:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-06 17:31 [Qemu-devel] [Patch 3/4] [RFC] Zero Cluster Dedup, Offline dedup, qemu-img extentions Shahar Frank
2008-10-06 17:46 ` Daniel P. Berrange [this message]
2008-10-07  9:17   ` Shahar Frank

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=20081006174606.GW20979@redhat.com \
    --to=berrange@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).