Home
last modified time | relevance | path

Searched hist:"91 bfcdb01d4869aa8f4cb67007827de63b8c2217" (Results 1 – 3 of 3) sorted by relevance

/openbmc/qemu/crypto/
H A Dinit.c91bfcdb01d4869aa8f4cb67007827de63b8c2217 Fri Oct 16 10:36:53 CDT 2015 Daniel P. Berrange <berrange@redhat.com> crypto: allow use of nettle/gcrypt to be selected explicitly

Currently the choice of whether to use nettle or gcrypt is
made based on what gnutls is linked to. There are times
when it is desirable to be able to force build against a
specific library. For example, if testing changes to QEMU's
crypto code all 3 possible backends need to be checked
regardless of what the local gnutls uses.

It is also desirable to be able to enable nettle/gcrypt
for cipher/hash algorithms, without enabling gnutls
for TLS support.

This gives two new configure flags, which allow the
following possibilities

Automatically determine nettle vs gcrypt from what
gnutls links to (recommended to minimize number of
crypto libraries linked to)

./configure

Automatically determine nettle vs gcrypt based on
which is installed

./configure --disable-gnutls

Force use of nettle

./configure --enable-nettle

Force use of gcrypt

./configure --enable-gcrypt

Force use of built-in AES & crippled-DES

./configure --disable-nettle --disable-gcrypt

Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
H A Dcipher.c91bfcdb01d4869aa8f4cb67007827de63b8c2217 Fri Oct 16 10:36:53 CDT 2015 Daniel P. Berrange <berrange@redhat.com> crypto: allow use of nettle/gcrypt to be selected explicitly

Currently the choice of whether to use nettle or gcrypt is
made based on what gnutls is linked to. There are times
when it is desirable to be able to force build against a
specific library. For example, if testing changes to QEMU's
crypto code all 3 possible backends need to be checked
regardless of what the local gnutls uses.

It is also desirable to be able to enable nettle/gcrypt
for cipher/hash algorithms, without enabling gnutls
for TLS support.

This gives two new configure flags, which allow the
following possibilities

Automatically determine nettle vs gcrypt from what
gnutls links to (recommended to minimize number of
crypto libraries linked to)

./configure

Automatically determine nettle vs gcrypt based on
which is installed

./configure --disable-gnutls

Force use of nettle

./configure --enable-nettle

Force use of gcrypt

./configure --enable-gcrypt

Force use of built-in AES & crippled-DES

./configure --disable-nettle --disable-gcrypt

Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
/openbmc/qemu/
H A Dconfigure91bfcdb01d4869aa8f4cb67007827de63b8c2217 Fri Oct 16 10:36:53 CDT 2015 Daniel P. Berrange <berrange@redhat.com> crypto: allow use of nettle/gcrypt to be selected explicitly

Currently the choice of whether to use nettle or gcrypt is
made based on what gnutls is linked to. There are times
when it is desirable to be able to force build against a
specific library. For example, if testing changes to QEMU's
crypto code all 3 possible backends need to be checked
regardless of what the local gnutls uses.

It is also desirable to be able to enable nettle/gcrypt
for cipher/hash algorithms, without enabling gnutls
for TLS support.

This gives two new configure flags, which allow the
following possibilities

Automatically determine nettle vs gcrypt from what
gnutls links to (recommended to minimize number of
crypto libraries linked to)

./configure

Automatically determine nettle vs gcrypt based on
which is installed

./configure --disable-gnutls

Force use of nettle

./configure --enable-nettle

Force use of gcrypt

./configure --enable-gcrypt

Force use of built-in AES & crippled-DES

./configure --disable-nettle --disable-gcrypt

Signed-off-by: Daniel P. Berrange <berrange@redhat.com>