From: "Ludovic Courtès" <ludo@gnu.org>
To: Sergey Bugaev <bugaevc@gmail.com>
Cc: squid3@treenet.co.nz, bug-hurd@gnu.org,
debian-hurd@lists.debian.org, jlledom@mailfence.com,
guix-devel@gnu.org, rbraun@sceen.net
Subject: Re: [VULN 0/4] Hurd vulnerability details
Date: Wed, 17 Nov 2021 11:45:42 +0100 [thread overview]
Message-ID: <87czmzysa1.fsf@gnu.org> (raw)
In-Reply-To: <20211109172843.kzijve7zykhl6soy@begin> (Samuel Thibault's message of "Tue, 9 Nov 2021 18:28:43 +0100")
Hi Samuel, Sergey, & all,
Samuel Thibault <samuel.thibault@gnu.org> skribis:
> Ludovic Courtès, le mar. 09 nov. 2021 18:19:03 +0100, a ecrit:
>> Am I right that the fixes have not been applied yet in the upstream
>> repository?
>
> That's right. That's still waiting for the copyright assignment.
How about making it the first contribution without FSF copyright
assignment?
The delay we observe here might be an outlier in FSF assignment
processing times, but regardless, it’s a good illustration of what a
project can lose by waiting for this long.
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-11-17 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 16:31 [VULN 0/4] Hurd vulnerability details Sergey Bugaev
2021-11-02 16:31 ` [VULN 1/4] Fake notifications Sergey Bugaev
2021-11-02 16:31 ` [VULN 2/4] No read-only mappings Sergey Bugaev
2021-11-02 16:31 ` [VULN 3/4] setuid exec race Sergey Bugaev
2021-11-02 16:31 ` [VULN 4/4] Process auth man-in-the-middle Sergey Bugaev
2021-11-02 16:35 ` [VULN 0/4] Hurd vulnerability details Samuel Thibault
2021-11-02 20:32 ` Vasileios Karaklioumis
2021-11-09 17:19 ` Ludovic Courtès
2021-11-09 17:28 ` Samuel Thibault
2021-11-17 10:45 ` Ludovic Courtès [this message]
2021-11-02 21:56 ` Guy-Fleury Iteriteka
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=87czmzysa1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-hurd@gnu.org \
--cc=bugaevc@gmail.com \
--cc=debian-hurd@lists.debian.org \
--cc=guix-devel@gnu.org \
--cc=jlledom@mailfence.com \
--cc=rbraun@sceen.net \
--cc=squid3@treenet.co.nz \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.