Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is a libsodium 1.0.19 release planned? #1028

Closed
past-due opened this issue Feb 2, 2021 · 1 comment
Closed

Is a libsodium 1.0.19 release planned? #1028

past-due opened this issue Feb 2, 2021 · 1 comment

Comments

@past-due
Copy link

past-due commented Feb 2, 2021

There have been a lot of improvements and fixes since the initial libsodium 1.0.18 release, and the rolling "libsodium 1.0.18-stable" releases are quite nice.

However, there are various situations in which having an immutable release tarball / Git tag are quite helpful (or required). And there are various downstreams that won't really pick up many / any of these improvements until the release number is incremented.

For those (and other) reasons, I'd like to kindly request consideration of making an official "1.0.19" release that packages up all of the improvements since that initial 1.0.18 release, when appropriate / possible.

(Also, a huge thank you for all the incredible work on a fantastic library. 🥳)

@jedisct1
Copy link
Owner

jedisct1 commented Feb 2, 2021

Yes, there will be more point releases.

The H2C specification being a moving target was one of the blockers, and the libsodium API for it just had to be changed a couple days ago due to discrepancies between that specification and the way it is used in protocols.

Better support for Apple Silicon, at least add AES-GCM and possibly faster AEGIS are also required for a new release. And support for batch signatures could be nice to have, too, if only for parity with the Zig standard library. But once done yes, a new version will be cut.

Meanwhile, you can always pin specific commits from stable.

@jedisct1 jedisct1 closed this as completed Feb 2, 2021
Repository owner locked and limited conversation to collaborators May 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants