From: "jgart" <jgart@dismail.de>
To: "Leo Famulari" <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: gunicorn and CVE-2024-1135
Date: Wed, 17 Jul 2024 21:21:53 +0000 [thread overview]
Message-ID: <651ba6daed4e305955a43dd1a20487bf95b8b1c5@dismail.de> (raw)
In-Reply-To: <ZpfVUVxsnVI37CMF@jasmine.lan>
> I'm not sure I understand the question. Gunicorn-next contains the CVE
>
> fix, but gunicorn does not? Is that correct?
Yep, that is correct. gunicorn does not contain the fix and gunicorn-next does contain the fix.
next prev parent reply other threads:[~2024-07-17 21:54 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 [this message]
2024-07-17 21:34 ` Leo Famulari
2024-07-18 2:40 ` jgart
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=651ba6daed4e305955a43dd1a20487bf95b8b1c5@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.