From: "jgart" <jgart@dismail.de>
To: "Leo Famulari" <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: gunicorn and CVE-2024-1135
Date: Thu, 18 Jul 2024 02:40:32 +0000 [thread overview]
Message-ID: <f1357f7bd1e5537644b6d13527d05586dfea32a1@dismail.de> (raw)
In-Reply-To: <Zpg4z3huRYmoys4X@jasmine.lan>
> Okay. Is there a reason to create gunicorn-next rather than updating
>
> gunicorn?
Hi Leo,
Yes, time. Updating the packages that depend on that bad gunicorn will take time which I don't have at the moment to fix them, unfortunately.
I might not be able to get to updating all those packages until maybe up to 2 or more weeks from now depending on how busy I am.
> Otherwise, Guix will not build, and we won't have successfully mitigated
>
> the vulnerability for our users.
Yep, I just made the gunicorn-next package available for anyone that wants to use it but it's not integrated into the dependents as listed by `guix refresh -l gunicorn@20.1.0`. It is standalone.
If anyone would like to work on it before I am able to get to it feel free.
I just thought I'd let people know here in case it is higher priority for anyone else.
all best,
jgart
prev parent reply other threads:[~2024-07-18 2:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 4:08 gunicorn and CVE-2024-1135 jgart
2024-07-17 14:29 ` Leo Famulari
2024-07-17 21:21 ` jgart
2024-07-17 21:34 ` Leo Famulari
2024-07-18 2:40 ` jgart [this message]
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=f1357f7bd1e5537644b6d13527d05586dfea32a1@dismail.de \
--to=jgart@dismail.de \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.