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

AESNI tracking ticket #106

Closed
karel-m opened this issue Jul 6, 2024 · 5 comments
Closed

AESNI tracking ticket #106

karel-m opened this issue Jul 6, 2024 · 5 comments

Comments

@karel-m
Copy link
Contributor

karel-m commented Jul 6, 2024

I have created this ticket as an umbrela issue over the following reported troubles:

Any improvements related to AESNI should go first to libtomcrypt. Once fixed there I will upgrade CryptX to the latest libtomcrypt version (branch develop).

@karel-m
Copy link
Contributor Author

karel-m commented Jul 6, 2024

@karel-m
Copy link
Contributor Author

karel-m commented Sep 2, 2024

@thesamesam @PyBonnetainNesterenko could you please check CryptX-0.080_010 ?

@karel-m
Copy link
Contributor Author

karel-m commented Sep 3, 2024

Try rather CryptX-0.080_012 which contains #107

@thesamesam
Copy link

I'll give it a look.

@karel-m
Copy link
Contributor Author

karel-m commented Sep 8, 2024

Shoutl be fixed in CryptX-0.081 which I have just released.

@karel-m karel-m closed this as completed Sep 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants