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
Deprecate and eventually get rid of support of NSS as a crypto backend #1041
Comments
- switch default to OpenSSL - warn about deprecation in the case NSS is selected during configuration Resolves: SSSD#1041 parts I.1 and I.2
|
Take a note, despite GH saying "linked a pull request that will close this issue", that's not the case - #1042 should not close this ticket. |
- switch default to OpenSSL - warn about deprecation in the case NSS is selected during configuration Resolves: SSSD#1041 parts I.1 and I.2
|
|
I will re-assign this ticket on @pbrezina awhile for "announce deprecation in the release notes of next upstream release" item. |
This item is done: https://sssd.github.io/docs/users/relnotes/notes_2_3_0.html |
|
Took ticket back to do (II) |
|
Hi @scabrero, could you please clarify what is the difference between:
What I actually want to figure out: will it cause any troubles for openSUSE packager if we will drop support of I guess it shouldn't, since every spec-file uses |
|
Hi @alexey-tikhonov, each release maintains its own spec file in the build system, we don't use in-tree spec files. As you said, switching to openSSL is not a problem as we build with Thanks for taking the time to ask. |
Resolves: SSSD#1041
Resolves: SSSD#1041
Resolves: SSSD#1041
Resolves: #1041 Reviewed-by: Pavel Březina <pbrezina@redhat.com>
Master branch should eventually drop support of libnss as a crypto backend.
Steps would be:
(I)
(II) finally remove support of libnss in (next+1) upstream release
The text was updated successfully, but these errors were encountered: