From: "Michael S. Tsirkin" <mst@redhat.com>
To: virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, "Cali,
Marco" <xmarcalx@amazon.co.uk>, "Graf (AWS),
Alexander" <graf@amazon.de>,
"Chalios, Babis" <bchalios@amazon.es>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: [virtio-dev] Re: [PATCH RFC 0/3] virtio-rng based entropy leak reporting
Date: Thu, 12 Jan 2023 02:02:49 -0500 [thread overview]
Message-ID: <20230112020204-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20221121162756.350032-1-mst@redhat.com>
On Mon, Nov 21, 2022 at 11:30:19AM -0500, Michael S. Tsirkin wrote:
> Generally, entropy only grows. However, there are cases where
> it goes down - for example, consider generating a one time
> pad where someone managed to use a side channel to
> steal its contents. By combining the seemingly random
> pad with the stolen contents we have reversed the entropy.
>
> This actually happens within VMs e.g. when time is reversed due
> to snapshoting. Existing approaches for VMs include Microsoft's
> VM GEN ID.
>
> This draft proposes a feature in virtio rng for reporting such
> leaks.
>
> Patches 1,2 refactor existing draft text. Patch 3 adds new functionality.
>
> TODO:
> document theory of operation
> add conformance clauses
Guys any input on this? Anyone going to use this?
>
> Michael S. Tsirkin (3):
> rng: move to a file of its own
> rng: be specific about the virtqueue
> rng: leak detection support
>
> content.tex | 43 +--------------------
> virtio-rng.tex | 102 +++++++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 103 insertions(+), 42 deletions(-)
> create mode 100644 virtio-rng.tex
>
> --
> MST
>
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-01-12 7:02 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 16:30 [virtio-comment] [PATCH RFC 0/3] virtio-rng based entropy leak reporting Michael S. Tsirkin
2022-11-21 16:30 ` [virtio-comment] [PATCH RFC 1/3] rng: move to a file of its own Michael S. Tsirkin
2022-11-21 16:30 ` [virtio-comment] [PATCH RFC 2/3] rng: be specific about the virtqueue Michael S. Tsirkin
2022-11-21 16:30 ` [virtio-dev] [PATCH RFC 3/3] rng: leak detection support Michael S. Tsirkin
2022-11-25 12:41 ` [virtio-dev] " Babis Chalios
2022-12-12 10:10 ` Babis Chalios
2023-01-11 13:57 ` Babis Chalios
2023-08-31 10:16 ` [virtio-dev] " Babis Chalios
2023-09-12 21:05 ` [virtio-comment] " Michael S. Tsirkin
2023-09-12 21:05 ` Michael S. Tsirkin
2023-09-13 9:32 ` Babis Chalios
2023-09-13 9:37 ` [virtio-comment] " Michael S. Tsirkin
2023-09-13 9:37 ` Michael S. Tsirkin
2023-09-13 11:19 ` Babis Chalios
2023-09-18 11:14 ` Babis Chalios
2023-09-18 12:41 ` [virtio-comment] " Michael S. Tsirkin
2023-09-18 12:41 ` Michael S. Tsirkin
2023-09-18 13:00 ` Babis Chalios
2023-09-18 13:58 ` [virtio-comment] " Michael S. Tsirkin
2023-09-18 13:58 ` Michael S. Tsirkin
2023-09-18 14:02 ` Babis Chalios
2023-09-18 14:05 ` [virtio-comment] " Michael S. Tsirkin
2023-09-18 14:05 ` Michael S. Tsirkin
2023-09-18 16:30 ` Babis Chalios
2023-09-19 7:32 ` Babis Chalios
2023-09-19 10:01 ` [virtio-comment] " Michael S. Tsirkin
2023-09-19 10:01 ` Michael S. Tsirkin
2023-09-19 10:11 ` Babis Chalios
2023-09-22 12:30 ` Babis Chalios
2023-09-22 15:06 ` [virtio-comment] " Michael S. Tsirkin
2023-09-22 15:06 ` Michael S. Tsirkin
2023-09-22 15:40 ` Babis Chalios
2023-09-22 16:01 ` [virtio-comment] " Michael S. Tsirkin
2023-09-22 16:01 ` Michael S. Tsirkin
2023-09-27 10:43 ` Babis Chalios
2023-09-27 21:47 ` [virtio-comment] " Michael S. Tsirkin
2023-09-27 21:47 ` Michael S. Tsirkin
2023-09-28 18:16 ` Babis Chalios
2023-10-13 7:49 ` Babis Chalios
2023-10-13 13:38 ` [virtio-comment] " Michael S. Tsirkin
2023-10-13 13:38 ` Michael S. Tsirkin
2023-11-02 11:20 ` [virtio-comment] " Michael S. Tsirkin
2023-11-02 11:20 ` Michael S. Tsirkin
2023-11-02 11:38 ` Babis Chalios
2023-11-02 11:51 ` [virtio-comment] " Michael S. Tsirkin
2023-11-02 11:51 ` Michael S. Tsirkin
2023-11-02 13:42 ` Babis Chalios
2023-11-02 11:25 ` [virtio-comment] " Michael S. Tsirkin
2023-11-02 11:25 ` Michael S. Tsirkin
2023-11-02 11:51 ` Babis Chalios
2023-01-12 7:02 ` Michael S. Tsirkin [this message]
2023-01-16 11:39 ` [virtio-dev] Re: [PATCH RFC 0/3] virtio-rng based entropy leak reporting Babis Chalios
[not found] ` <CAHmME9ry2fss2gsbPs2zVJkY=8Cdeae0XFD9FzCVnW67Xy3thA@mail.gmail.com>
2023-01-16 18:11 ` [virtio-comment] " Michael S. Tsirkin
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=20230112020204-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=Jason@zx2c4.com \
--cc=bchalios@amazon.es \
--cc=graf@amazon.de \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=xmarcalx@amazon.co.uk \
/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.