Ubuntu
liboqs package

Please do not ship liboqs in stable releases

Bug #1954379 reported by Andrius Merkys
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
liboqs (Debian)
New
Unknown
liboqs (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

The authors of liboqs have explicitly asked to withhold distribution of liboqs binary packages until the NIST Post-Quantum Cryptography standardization project reaches its conclusion. Please block liboqs binary packages from being shipped with stable Ubuntu releases.

I am the maintainer of liboqs in Debian, and there I have blocked the source package from migrating to testing branch (https://bugs.debian.org/1000303). It would be best to block liboqs until the bug report in Debian is closed.

Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thanks for reporting.

I've taken the liberty of subscribing the Archive Admins to take a look at this. They can remove the package from upcoming release, and I believe there is a magical tag to keep new versions from migrating from proposed.

Bug Watch Updater (bug-watch-updater)
Changed in liboqs (Debian):
status: Unknown → New
Revision history for this message
Steve Langasek (vorlon) wrote :

Removing packages from jammy:
 liboqs 0.7.1~rc1-1 in jammy
  liboqs-dev 0.7.1~rc1-1 in jammy amd64
  liboqs-dev 0.7.1~rc1-1 in jammy arm64
  liboqs-dev 0.7.1~rc1-1 in jammy armhf
  liboqs-dev 0.7.1~rc1-1 in jammy ppc64el
  liboqs-dev 0.7.1~rc1-1 in jammy riscv64
  liboqs-dev 0.7.1~rc1-1 in jammy s390x
  liboqs0 0.7.1~rc1-1 in jammy amd64
  liboqs0 0.7.1~rc1-1 in jammy arm64
  liboqs0 0.7.1~rc1-1 in jammy armhf
  liboqs0 0.7.1~rc1-1 in jammy ppc64el
  liboqs0 0.7.1~rc1-1 in jammy riscv64
  liboqs0 0.7.1~rc1-1 in jammy s390x
Comment: Not for stable release
1 package successfully removed.

Leaving the bug report open so that any further source uploads also remain blocked. Thanks!

tags: added: block-proposed
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in liboqs (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.