From: Michael Richardson <mcr@sandelman.ca>
To: Patrick Williams <patrick@stwcx.xyz>,
Joseph Reynolds <jrey@linux.ibm.com>,
openbmc <openbmc@lists.ozlabs.org>,
"mail@thson.de" <mail@thson.de>
Subject: Re: Security Working Group meeting - Wednesday August 31 - results
Date: Thu, 01 Sep 2022 17:23:01 -0400 [thread overview]
Message-ID: <16276.1662067381@localhost> (raw)
In-Reply-To: <YxCWpNZ+O89B+ulA@heinlein.stwcx.org.github.beta.tailscale.net>
[-- Attachment #1: Type: text/plain, Size: 172 bytes --]
My understanding is that keylime is being rewritten in Rust.
(but, it was a comment made in possing, which maybe I misunderstood)
{Also IETF RATS Architecture editor...}
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2022-09-01 21:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 1:08 Security Working Group meeting - Wednesday August 31 Joseph Reynolds
2022-08-31 1:16 ` Security Working Group meeting - Wednesday August 31 - new venue Joseph Reynolds
2022-08-31 18:09 ` Security Working Group meeting - Wednesday August 31 - results Joseph Reynolds
2022-09-01 11:25 ` Patrick Williams
2022-09-01 12:41 ` Brad Bishop
2022-09-01 15:07 ` Patrick Williams
2022-09-05 19:04 ` Joseph Reynolds
2022-09-01 21:23 ` Michael Richardson [this message]
2022-09-02 16:07 ` Thore Sommer
2022-09-06 13:10 ` Patrick Williams
2022-09-05 18:56 ` Joseph Reynolds
2022-09-06 8:05 ` Michael Richardson
2022-09-06 13:09 ` Patrick Williams
2022-09-12 19:31 ` George Almasi
2022-09-06 13:07 ` Patrick Williams
2022-09-07 8:01 ` Michael Richardson
2022-09-01 11:27 ` Patrick Williams
2022-09-05 18:59 ` Joseph Reynolds
2022-09-06 20:16 ` Patrick Williams
-- strict thread matches above, loose matches on Subject: below --
2022-09-08 18:57 George Almasi
[not found] ` <101586.1662709990@dooku>
2022-09-09 18:49 ` George Almasi
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=16276.1662067381@localhost \
--to=mcr@sandelman.ca \
--cc=jrey@linux.ibm.com \
--cc=mail@thson.de \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
/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.