From: Kees Cook <keescook@chromium.org>
To: Andrew Donnellan <ajd@linux.ibm.com>
Cc: linux-hardening@vger.kernel.org
Subject: Re: Kernel Self-Protection Project meeting
Date: Thu, 12 Jan 2023 13:36:07 -0800 [thread overview]
Message-ID: <202301121333.D4395FE3@keescook> (raw)
In-Reply-To: <5af2c54b767e2d314041dc77378c492ed44eaacf.camel@linux.ibm.com>
On Thu, Jan 12, 2023 at 04:44:26PM +1100, Andrew Donnellan wrote:
> Hi Kees,
>
> On Wed, 2023-01-11 at 08:27 -0800, Kees Cook wrote:
> > On Wed, Jan 11, 2023 at 08:23:39AM -0800, Kees Cook wrote:
> > > Hi!
> > >
> > > This is rather short notice; I'll send out a reminder further in
> > > advance
> > > next time, but if anyone would like to join our every-2-weeks
> > > project
> > > video conference, please drop in:
> > >
> > > https://meet.google.com/cuu-hqcm-ggg
>
> This is a great idea!
>
> Were there any notes taken from today's call?
Yes, I kept some limited notes, but tried to include URLs for stuff that
got talked about. I'm building a place to keep them that is more
change-control friendly besides a google doc. :) I'll finish getting
that built and get it published soon.
> > *cough* at 10am US Pacific today...
>
> Is it anticipated that the meetings will consistently be at 10am
> PST/PDT or will that move around a bit?
That's the current plan for now (but see below), every 2 weeks at 10am
US Pacific. If there's a good reason to move it around, we can certainly
do that.
> (I realise I'm a very quiet lurker on this list, but I am interested in
> occasionally dropping in when I can; 10am PST is a bit tricky here in
> +1100 territory but I'll still try.)
Yeah, once we've gotten the hang of it, I'd like to maybe shift it
around so it's more AU friendly with some regularlity.
--
Kees Cook
prev parent reply other threads:[~2023-01-12 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 16:23 Kernel Self-Protection Project meeting Kees Cook
2023-01-11 16:27 ` Kees Cook
2023-01-12 5:44 ` Andrew Donnellan
2023-01-12 21:36 ` Kees Cook [this message]
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=202301121333.D4395FE3@keescook \
--to=keescook@chromium.org \
--cc=ajd@linux.ibm.com \
--cc=linux-hardening@vger.kernel.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