-
Notifications
You must be signed in to change notification settings - Fork 463
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
New relese? #568
Comments
I second this request, for the same reason. |
we also need a new release. |
Hello all, Is there a current development for the library or it stopped by the last release in 2018? |
@babelouest could you please check whether we could still make it for debian 12 if we tagged either
I don't think so, but still asking whether it'd maybe be worth the effort... |
Hello @sjaeckel , I've tested both branches master and In the branch Both branches are in the salsa repo:
Do you want to run other tests with the debian package? |
Cool, thanks. Could you please check libtom/libtommath#418 (comment) and recreate what @dod38fr did with the two library versions? I'm nearly certain that ltc would also need an ABI major bump, which in turn would also mean that we won't be able to bring it to Bookworm!? |
Indeed, the symbols file will have a huge change, I haven't seen it yesterday. The library will probably need a transition process before migrating to testing. Due to the timing, I'm not sure the new version will be available in Bookworm though, because it requires a new release, then the new package will need to go through the NEW queue process. |
And no new transition will be possible after jan 12th due to first stage of freeze. |
@sjaeckel is there an upcoming release for libtomcrypt in the near future? |
I'm also looking for a new release that includes the fix for CVE-2019-17362 |
I will have a look next week. |
Dear @libtom team, We are in 2024, the latest release build is 1.18.2 (2018-07-02) - 6 years, 2 moths soon: It is time to create a new release build with CVE-2019-17362 fix! Thanks in advance. PS: Thanks to @kloczek for this ticket from 2021-04-19 - 3 years, 4 months already. |
FTR: even though @kloczek is right and this library should get a new release - I've blocked @Neustradamus from this organisation and all the others I have access to. A short version of why: sjaeckel/sjaeckel.github.io#1 |
Is it possible to make new release soon?
I'm asking because lat latest perl CryptX seems is using featires which are not included in 1.18.2 and are only available in commits added after last release.
Here is build fail log on building perl CryptX against libtomcrypt 1.18.2.
The text was updated successfully, but these errors were encountered: