debcrafters-packages team mailing list archive

[Tobias Heider <2120496@xxxxxxxxxxxxxxxxxx>]

I think we should do this. Regression potential seems low as it would
only introduce and alias for the now standardized name. The key exchange
itself under a openssh private name is already available and enabled on
Jammy and Noble.

For the record the commits are:
  Noble:
    https://github.com/openssh/openssh-portable/commit/4306a0ccb712249c98c0ab1a8ad4bf0761be4011
    https://github.com/openssh/openssh-portable/commit/68b5963fea1d421821648734096f5d5e0492663a

  Jammy:
    https://github.com/openssh/openssh-portable/commit/ffdbae4c0201d42bfa1f5c5e9c21454d10795491
    https://github.com/openssh/openssh-portable/commit/b738f18f4b26cbd92cd0dfcff960d5f2ee7c0f9

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2120496

Title:
  Consider enabling sntrup761x25519-sha512 post-quantum algorithm for
  stable releases

Status in openssh package in Ubuntu:
  New

Bug description:
  openssh upstream recently posted[1] about a series of patches made
  available for openssh stable releases to enable the
  sntrup761x25519-sha512 post-quantum key-exchange algorithm.

  This bug is a placeholder to evaluate this opportunity, and check
  which ubuntu releases could benefit from this. Given the version
  numbers in that post, it looks like jammy and noble could benefit.

  1. https://lists.mindrot.org/pipermail/openssh-unix-
  dev/2025-August/042030.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2120496/+subscriptions