* glibc status update - Week ending January 31st.
@ 2025-02-26 13:12 Carlos O'Donell
0 siblings, 0 replies; only message in thread
From: Carlos O'Donell @ 2025-02-26 13:12 UTC (permalink / raw)
To: cti-tac
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2025-02-26 13:12 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-02-26 13:12 glibc status update - Week ending January 31st Carlos O'Donell
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.