public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Noah Goldstein <goldstein.w.n@gmail.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: GNU C Library <libc-alpha@sourceware.org>,
	"Carlos O'Donell" <carlos@redhat.com>,
	 Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: [RFC] Publishing glibc advisories
Date: Thu, 12 Oct 2023 17:59:26 -0500	[thread overview]
Message-ID: <CAFUsyf+G43TMegFinpbfHJb=C-bixZiHscJcmVG4qifUizqhGg@mail.gmail.com> (raw)
In-Reply-To: <6a081acc-0faa-c2fb-c99d-5a44bbbd2496@gotplt.org>

On Thu, Oct 12, 2023 at 5:25 PM Siddhesh Poyarekar <siddhesh@gotplt.org> wrote:
>
> On 2023-10-12 18:09, Noah Goldstein wrote:
> > Personally would think it makes more sense to keep in the current repo.
> > Not everyone checking out the code will know to look for glibc-advisories.git
> > so it just seems liable to cause people to miss them.
>
> Oh so the code would continue to have the information it currently does,
> e.g. CVE numbers in the commits and in NEWS.  This is for additional
> information that gets announced as advisories, that refer to, e.g.
> commits in the repository that contributed to fixing the CVE, branches
> the fixes were backported to, etc.  Here are some example announcements:
>
> https://www.openwall.com/lists/oss-security/2023/10/11/1
> https://mail.python.org/archives/list/security-announce@python.org/thread/TRTM4UVSANUWNHC2QY2X73E5IBQLQU76/
> https://www.openwall.com/lists/oss-security/2023/10/10/9
>

I see, so the expectation is all actionable information would be in the glibc
git, and the purely information stuff would be in advisories-glibc.git? If so
that seems reasonable.

> All of them admittedly share different amounts of information, but I was
> hoping for us to be as informative as possible.
>
> Thanks,
> Sid

  reply	other threads:[~2023-10-12 22:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 21:50 Siddhesh Poyarekar
2023-10-12 22:09 ` Noah Goldstein
2023-10-12 22:24   ` Siddhesh Poyarekar
2023-10-12 22:59     ` Noah Goldstein [this message]
2023-10-13  0:43       ` Siddhesh Poyarekar
2023-10-12 23:26 ` DJ Delorie
2023-10-13  0:43   ` Siddhesh Poyarekar
2023-10-13  1:51     ` Frank Ch. Eigler
2023-10-13  7:40 ` Florian Weimer
2023-10-13 10:50   ` Siddhesh Poyarekar
2023-11-07 15:03     ` Florian Weimer

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='CAFUsyf+G43TMegFinpbfHJb=C-bixZiHscJcmVG4qifUizqhGg@mail.gmail.com' \
    --to=goldstein.w.n@gmail.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@gotplt.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).