All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Alexander Dahl <post@lespocky.de>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/putty: security bump to version 0.81
Date: Sat, 08 Jun 2024 15:53:49 +0200	[thread overview]
Message-ID: <87le3f35hu.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20240516163144.640424-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Thu, 16 May 2024 18:31:44 +0200")

>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:

 > The only change between 0.80 and 0.81 is one security fix:
 >  - ECDSA signatures using 521-bit keys (the NIST P521 curve, otherwise
 >    known as ecdsa-sha2-nistp521) were generated with biased random
 >    numbers. This permits an attacker in possession of a few dozen
 >    signatures to RECOVER THE PRIVATE KEY.

 >    Any 521-bit ECDSA private key that PuTTY or Pageant has used to
 >    sign anything should be considered compromised.

 >    This vulnerability has the identifier CVE-2024-31497.

 > Update hash of LICENCE file (update in year with
 > https://git.tartarus.org/?p=simon/putty.git;a=commit;h=f2f28ac0386eebbd45ea605818d31d62d219f589)

 > https://lists.tartarus.org/pipermail/putty-announce/2024/000038.html

 > Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

Committed to 2024.02.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2024-06-08 13:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16 16:31 [Buildroot] [PATCH 1/1] package/putty: security bump to version 0.81 Fabrice Fontaine
2024-05-24 12:32 ` Peter Korsgaard
2024-06-08 13:53 ` 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=87le3f35hu.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=post@lespocky.de \
    /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.