-
Notifications
You must be signed in to change notification settings - Fork 387
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 kazoo release to include SSL fixes #720
Comments
Hello, Thank you for the issue. I believe a new release would be cut soon, on my side I was waiting on #681 to land so that our Windows users can enjoy the lib in its latest version. |
Would there be appetite for #685 to be merged for that new release?
…On Wed, May 24, 2023, 09:02 Stephen Sorriaux ***@***.***> wrote:
Hello,
Thank you for the issue.
I believe a new release would be cut soon, on my side I was waiting on
#681 <#681> to land so that our
Windows users can enjoy the lib in its latest version.
I am just curious: have you been able to try the current master branch?
—
Reply to this email directly, view it on GitHub
<#720 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIFTHWIP6TBTSPISTG4OYTXHYBFPANCNFSM6AAAAAAYKSJGG4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I have, but only locally / in dev - and ofc it works great! For context: prod releases require our images based on RedHat UBI with FIPS enabled, which make testing "is this a FIPS issue?" problems trivial - just |
Hello, Just wanted to give a heads up that the 2.10.0 release is here now. |
What would you like to be added
#706 , fixes various SSL methods that where deprecated in python3.10. Yay! The PR was merged in Feb 2023, any chance of a new kazoo release that incorporates this PR?
Why is this needed
While the warnings are merely annoying, we're running kazoo in a FIPS enabled environment, where any TLS / SSL issues (or warnings) become much more serious from an auditing perspective. We'd love to bump our kazoo dependencies to the next version to mitigate these admittedly corporate problems :) Any plans / timelines for a new kazoo release?
The text was updated successfully, but these errors were encountered: