From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Asaf Kahlon <asafka7@gmail.com>,
James Hilliard <james.hilliard1@gmail.com>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/python-paramiko: security bump to version 3.4.0
Date: Fri, 12 Jan 2024 16:21:29 +0100 [thread overview]
Message-ID: <87v87y1ssm.fsf@48ers.dk> (raw)
In-Reply-To: <20240102095510.395f7b6f@windsurf> (Thomas Petazzoni via buildroot's message of "Tue, 2 Jan 2024 09:55:10 +0100")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> On Mon, 1 Jan 2024 23:13:17 +0100
> Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
>> Address CVE 2023-48795 (aka the “Terrapin Attack”, a vulnerability found
>> in the SSH protocol re
>>
>> https://github.com/paramiko/paramiko/blob/3.4.0/sites/www/changelog.rst
>>
>> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
>> ---
>> package/python-paramiko/python-paramiko.hash | 4 ++--
>> package/python-paramiko/python-paramiko.mk | 4 ++--
>> 2 files changed, 4 insertions(+), 4 deletions(-)
> Applied to master, thanks.
FYI, 2023.02.x and 2023.11.x has paramiko 2.12. I would prefer to not
have to bump them to 3.4.0.
I see that Debian also has paramiko 2.12, but so far no backported patch
for it. Hopefully that will show up soon:
https://security-tracker.debian.org/tracker/CVE-2023-48795
So I'll leave this for now.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-01-12 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 22:13 [Buildroot] [PATCH 1/1] package/python-paramiko: security bump to version 3.4.0 Fabrice Fontaine
2024-01-02 8:55 ` Thomas Petazzoni via buildroot
2024-01-12 15:21 ` Peter Korsgaard [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=87v87y1ssm.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=asafka7@gmail.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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 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.