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: 23+ 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
[not found] ` <0abb7518-16e0-4227-bfe1-a29bd27124e8@amazon.es>
2023-09-12 21:05 ` [virtio-comment] Re: [virtio-dev] " Michael S. Tsirkin
[not found] ` <e738e7f0-dd13-44db-806c-543746aa6967@amazon.es>
2023-09-13 9:37 ` Michael S. Tsirkin
[not found] ` <d7d17e9f-e6ad-4106-a408-99281382a93f@amazon.es>
2023-09-18 12:41 ` Michael S. Tsirkin
[not found] ` <e75d9667-2ea0-44d0-a26f-fa3d5fe05651@amazon.es>
2023-09-18 13:58 ` Michael S. Tsirkin
[not found] ` <a22ba2cb-9b03-481a-b66e-0b78fbfb21f0@amazon.es>
2023-09-18 14:05 ` Michael S. Tsirkin
[not found] ` <4ab1b10e-4524-4b6c-a3df-863360fd225d@amazon.es>
[not found] ` <c2e7076b-b07e-43cd-a912-9314d742a678@amazon.es>
2023-09-19 10:01 ` Michael S. Tsirkin
[not found] ` <4c6d6710-43c8-402b-9ae6-d2f4cafbe9a7@amazon.es>
2023-09-22 15:06 ` Michael S. Tsirkin
[not found] ` <c0c5b159-997f-4ddf-ab3e-1c749ad93e10@amazon.es>
2023-09-22 16:01 ` Michael S. Tsirkin
[not found] ` <19967fde-8893-4fe8-9f9a-7ce49bf38772@amazon.es>
2023-09-27 21:47 ` Michael S. Tsirkin
[not found] ` <4d22d699-b9f3-4d67-940a-8f11bcd29819@amazon.es>
[not found] ` <5f548d39-2ae4-45a8-9dba-49a2c693dae4@amazon.es>
2023-10-13 13:38 ` Michael S. Tsirkin
2023-11-02 11:20 ` Michael S. Tsirkin
[not found] ` <23ca2091-efd8-498d-8ed6-9ac4fb905f1d@amazon.es>
2023-11-02 11:51 ` Michael S. Tsirkin
2023-11-02 11:25 ` Michael S. Tsirkin
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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox