From: Carlos O'Donell <carlos@redhat.com>
To: cti-tac@lists.linuxfoundation.org
Subject: glibc status update - Week ending January 31st.
Date: Wed, 26 Feb 2025 08:12:43 -0500 [thread overview]
Message-ID: <29ffeff2-ea80-4b61-96fc-bc75fbfd7b77@redhat.com> (raw)
At the last CTI TAC meeting I decided to switch to weekly reporting on the
progress I'm making going through and creating the justifying glibc policy
for the CTI changes we're requesting.
I'm driving this from the NIST SP 800-218 perspective which has a good
framework for making these kinds of decision, and has all sorts of places
to state what and why we want and need those changes.
Current status looks like this:
PO [In progress] 13 sections.
- Started PO.1.1 "Identify and document all security requirements"
PS [not started] 4 sections.
PW [not started] 16 sections.
RV [not started] 9 sections.
Note: Sending these out backdated.
--
Cheers,
Carlos.
reply other threads:[~2025-02-26 13:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=29ffeff2-ea80-4b61-96fc-bc75fbfd7b77@redhat.com \
--to=carlos@redhat.com \
--cc=cti-tac@lists.linuxfoundation.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 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.