qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: [Qemu-devel] [PULL v1 0/5] Support for securely passing secrets to QEMU
Date: Fri, 18 Dec 2015 16:53:15 +0000	[thread overview]
Message-ID: <1450457600-19865-1-git-send-email-berrange@redhat.com> (raw)

The following changes since commit 18f49881cf8359e89396aac12f5d3cf3f8a632ba:

  configure: Fix shell syntax to placate OpenBSD's pdksh (2015-12-18 13:32:49 +0000)

are available in the git repository at:

  git://github.com/berrange/qemu tags/pull-qcrypto-secrets-base-2015-12-18-1

for you to fetch changes up to 1d7b5b4afdcd76e24ec3678d5418b29d4ff06ad9:

  crypto: add support for loading encrypted x509 keys (2015-12-18 16:25:08 +0000)

----------------------------------------------------------------
Merge QCryptoSecret object support

----------------------------------------------------------------
Daniel P. Berrange (5):
      util: add base64 decoding function
      qemu-char: convert to use error checked base64 decode
      qga: convert to use error checked base64 decode
      crypto: add QCryptoSecret object class for password/key handling
      crypto: add support for loading encrypted x509 keys

 crypto/Makefile.objs          |   1 +
 crypto/secret.c               | 513 ++++++++++++++++++++++++++++++++++++++++++
 crypto/tlscredsx509.c         |  48 ++++
 include/crypto/secret.h       | 148 ++++++++++++
 include/crypto/tlscredsx509.h |   1 +
 include/qemu/base64.h         |  58 +++++
 qapi-schema.json              |   2 -
 qapi/crypto.json              |  14 ++
 qemu-char.c                   |   8 +-
 qemu-options.hx               |  85 ++++++-
 qga/commands-posix.c          |  11 +-
 qga/commands-win32.c          |  11 +-
 qga/commands.c                |  13 +-
 qmp-commands.hx               |   2 -
 tests/.gitignore              |   2 +
 tests/Makefile                |   5 +
 tests/test-base64.c           | 109 +++++++++
 tests/test-crypto-secret.c    | 452 +++++++++++++++++++++++++++++++++++++
 util/Makefile.objs            |   1 +
 util/base64.c                 |  60 +++++
 20 files changed, 1533 insertions(+), 11 deletions(-)
 create mode 100644 crypto/secret.c
 create mode 100644 include/crypto/secret.h
 create mode 100644 include/qemu/base64.h
 create mode 100644 tests/test-base64.c
 create mode 100644 tests/test-crypto-secret.c
 create mode 100644 util/base64.c

-- 
2.5.0

             reply	other threads:[~2015-12-18 16:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18 16:53 Daniel P. Berrange [this message]
2015-12-18 16:53 ` [Qemu-devel] [PULL v1 1/5] util: add base64 decoding function Daniel P. Berrange
2015-12-18 16:53 ` [Qemu-devel] [PULL v1 2/5] qemu-char: convert to use error checked base64 decode Daniel P. Berrange
2015-12-18 16:53 ` [Qemu-devel] [PULL v1 3/5] qga: " Daniel P. Berrange
2021-08-09 12:51   ` Peter Maydell
2015-12-18 16:53 ` [Qemu-devel] [PULL v1 4/5] crypto: add QCryptoSecret object class for password/key handling Daniel P. Berrange
2015-12-18 16:53 ` [Qemu-devel] [PULL v1 5/5] crypto: add support for loading encrypted x509 keys Daniel P. Berrange
2015-12-18 17:42 ` [Qemu-devel] [PULL v1 0/5] Support for securely passing secrets to QEMU Peter Maydell

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=1450457600-19865-1-git-send-email-berrange@redhat.com \
    --to=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).