From: Kees Cook <keescook@chromium.org>
To: linux-hardening@vger.kernel.org
Subject: Kernel Self-Protection Project meeting
Date: Wed, 11 Jan 2023 08:23:39 -0800 [thread overview]
Message-ID: <202301110820.C6020B71EA@keescook> (raw)
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
We'll be going over status updates and a little bit of planning for
2023. If you're working on any security things, come tell us about it.
:)
See you there!
-Kees
--
Kees Cook
next reply other threads:[~2023-01-11 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 16:23 Kees Cook [this message]
2023-01-11 16:27 ` Kernel Self-Protection Project meeting Kees Cook
2023-01-12 5:44 ` Andrew Donnellan
2023-01-12 21:36 ` Kees Cook
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=202301110820.C6020B71EA@keescook \
--to=keescook@chromium.org \
--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