From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: [Qemu-devel] [PULL v1 1/2] crypto: fix typo in docs for secret object type
Date: Tue, 5 Apr 2016 10:55:51 +0100 [thread overview]
Message-ID: <1459850152-19437-2-git-send-email-berrange@redhat.com> (raw)
In-Reply-To: <1459850152-19437-1-git-send-email-berrange@redhat.com>
The docs for the secret object type specified the wrong number
of bytes for the AES initialization vector.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
---
qemu-options.hx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/qemu-options.hx b/qemu-options.hx
index 789d9f6..587de8f 100644
--- a/qemu-options.hx
+++ b/qemu-options.hx
@@ -3888,7 +3888,7 @@ parameter provides the ID of a previously defined secret that contains
the AES-256 decryption key. This key should be 32-bytes long and be
base64 encoded. The @var{iv} parameter provides the random initialization
vector used for encryption of this particular secret and should be a
-base64 encrypted string of the 32-byte IV.
+base64 encrypted string of the 16-byte IV.
The simplest (insecure) usage is to provide the secret inline
--
2.5.5
next prev parent reply other threads:[~2016-04-05 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 9:55 [Qemu-devel] [PULL v1 0/2] QCrypto fixes for 2.6.0-rc1 Daniel P. Berrange
2016-04-05 9:55 ` Daniel P. Berrange [this message]
2016-04-05 9:55 ` [Qemu-devel] [PULL v1 2/2] crypto: fix nettle config check for running pbkdf test Daniel P. Berrange
2016-04-05 11:56 ` [Qemu-devel] [PULL v1 0/2] QCrypto fixes for 2.6.0-rc1 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=1459850152-19437-2-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).