linux-coco.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Stefano Garzarella <sgarzare@redhat.com>
To: svsm-devel@coconut-svsm.dev
Cc: linux-coco@lists.linux.dev, "Jörg Rödel" <joro@8bytes.org>
Subject: Re: [svsm-devel] SVSM Development Call April 3rd, 2024
Date: Wed, 3 Apr 2024 19:06:26 +0200	[thread overview]
Message-ID: <CAGxU2F5qTMU1hx-qAdc0ZL6mWoxWU1JhCTZK243KnMA29AiHFA@mail.gmail.com> (raw)
In-Reply-To: <Zg07c6Y5a_Ak5oXs@8bytes.org>

On Wed, Apr 3, 2024 at 1:20 PM Jörg Rödel <joro@8bytes.org> wrote:
>
> Hi,
>
> Here is the usual call for agenda items for this weeks SVSM development
> call. My agenda so far is:
>
>         * vTPM merge fallout
>         * Security issue mitigations

As I mentioned during the call, I started a shared document to discuss
early attestation architecture in SVSM:
https://docs.google.com/document/d/11ZsxP8jsviP3ddp9Hrn0rf6inttNw_Pbnz0psXlxlPs

To get write access, please send me a request.
The document is really at an early stage. As Jörg suggested, we're
keeping it on gdoc for now to collaborate, but as soon as we have an
agreement, we'll move to github in some markdown files.

As I mentioned, from next week (April 9th to be precise) I will be
away until the end of the month. I will be back online on May 3rd.
Sorry in advance for the delay in my responses.

Thanks,
Stefano

>
> The items we can not cover during the meeting will be deferred to the
> next meeting.
>
> Please note that Europe is now also on summer time, so the meeting will
> be at its usual time spot again. The definitive time is always in the
> Google calendar I shared below.
>
> Details of the meeting (GMeet and Calendar links, meeting time) can be
> found in our governance repository at:
>
>         https://github.com/coconut-svsm/governance
>
> The meeting will be recorded and the recording eventually published.
>
> See you all there.
>
> Regards,
>
>         Jörg
> --
> Svsm-devel mailing list
> Svsm-devel@coconut-svsm.dev
> https://mail.8bytes.org/cgi-bin/mailman/listinfo/svsm-devel
>


  parent reply	other threads:[~2024-04-03 17:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 11:20 SVSM Development Call April 3rd, 2024 Jörg Rödel
2024-04-03 11:59 ` Yao, Jiewen
2024-04-03 12:18   ` James Bottomley
2024-04-03 13:11     ` Yao, Jiewen
2024-04-03 17:06 ` Stefano Garzarella [this message]
2024-04-04  8:04 ` [svsm-devel] " Jörg Rödel

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=CAGxU2F5qTMU1hx-qAdc0ZL6mWoxWU1JhCTZK243KnMA29AiHFA@mail.gmail.com \
    --to=sgarzare@redhat.com \
    --cc=joro@8bytes.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=svsm-devel@coconut-svsm.dev \
    /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).