From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [PULL 0/5] Qcrypto next patches
Date: Fri, 29 May 2020 18:08:30 +0100 [thread overview]
Message-ID: <20200529170830.GK2755532@redhat.com> (raw)
In-Reply-To: <20200529103555.2759928-1-berrange@redhat.com>
On Fri, May 29, 2020 at 11:35:50AM +0100, Daniel P. Berrangé wrote:
> The following changes since commit b8bee16e94df0fcd03bdad9969c30894418b0e6e:
>
> Merge remote-tracking branch 'remotes/kraxel/tags/vga-20200528-pull-request=
> ' into staging (2020-05-28 18:13:20 +0100)
>
> are available in the Git repository at:
>
> https://github.com/berrange/qemu tags/qcrypto-next-pull-request
>
> for you to fetch changes up to efd6cd2328064b569a7a92ad4aea1dc985d98601:
>
> crypto: Remove use of GCRYPT_VERSION macro. (2020-05-29 11:33:19 +0100)
>
> ----------------------------------------------------------------
> Misc crypto subsystem fixes
>
> * Add support for fetching secret from Linux keyring
> * Remove redundant version check in gcrypt initialization
> * Allow for RNG provider to be disabled at build time
>
> ----------------------------------------------------------------
>
> Alexey Krasikov (3):
> crypto/secret: move main logic from 'secret' to 'secret_common'.
> crypto/linux_keyring: add 'secret_keyring' secret object.
> test-crypto-secret: add 'secret_keyring' object tests.
>
> Marek Marczykowski-G=C3=B3recki (1):
> crypto: add "none" random provider
>
> Richard W.M. Jones (1):
> crypto: Remove use of GCRYPT_VERSION macro.
>
> configure | 73 ++++++
> crypto/Makefile.objs | 5 +-
> crypto/init.c | 2 +-
> crypto/random-none.c | 38 +++
> crypto/secret.c | 347 +--------------------------
> crypto/secret_common.c | 403 ++++++++++++++++++++++++++++++++
> crypto/secret_keyring.c | 148 ++++++++++++
> include/crypto/secret.h | 20 +-
> include/crypto/secret_common.h | 68 ++++++
> include/crypto/secret_keyring.h | 52 +++++
> tests/Makefile.include | 4 +
> tests/test-crypto-secret.c | 158 +++++++++++++
> 12 files changed, 959 insertions(+), 359 deletions(-)
> create mode 100644 crypto/random-none.c
> create mode 100644 crypto/secret_common.c
> create mode 100644 crypto/secret_keyring.c
> create mode 100644 include/crypto/secret_common.h
> create mode 100644 include/crypto/secret_keyring.h
Seems the mingw build is broken due to mistakes in configure, so
i'll respin this.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2020-05-29 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 10:35 [PULL 0/5] Qcrypto next patches Daniel P. Berrangé
2020-05-29 10:35 ` [PULL 1/5] crypto: add "none" random provider Daniel P. Berrangé
2020-05-29 10:35 ` [PULL 2/5] crypto/secret: move main logic from 'secret' to 'secret_common' Daniel P. Berrangé
2020-05-29 10:35 ` [PULL 3/5] crypto/linux_keyring: add 'secret_keyring' secret object Daniel P. Berrangé
2020-06-05 11:06 ` Daniel P. Berrangé
2020-05-29 10:35 ` [PULL 4/5] test-crypto-secret: add 'secret_keyring' object tests Daniel P. Berrangé
2020-05-29 10:35 ` [PULL 5/5] crypto: Remove use of GCRYPT_VERSION macro Daniel P. Berrangé
2020-05-29 17:04 ` [PULL 0/5] Qcrypto next patches no-reply
2020-05-29 17:08 ` Daniel P. Berrangé [this message]
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=20200529170830.GK2755532@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 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.