[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sssd-devel
Subject:    =?utf-8?b?W1NTU0Rd?= [sssd PR#833][comment] util/crypto/libcrypto: changed sss_hmac_sha1()
From:       alexey-tikhonov <sssd-github-notification () fedorahosted ! org>
Date:       2019-06-26 9:48:16
Message-ID: gh-SSSD/sssd-833-2019-ce26fcab-6240-42e9-acc8-f55398d7b9a1 () sssd-github-notification ! fedorahosted ! org
[Download RAW message or body]

[Attachment #2 (unknown)]

  URL: https://github.com/SSSD/sssd/pull/833
Title: #833: util/crypto/libcrypto: changed sss_hmac_sha1()

alexey-tikhonov commented:
"""
> @alexey-tikhonov please let me know if you'd prefer to have this patch backported \
> to sssd-1-16 as well. I can see both sides of the argument, on the one hand, we \
> shouldn't needlessly backport patches which might potentially cause issues in the \
> stable branch, OTOH not having these patches in a stable branch might cause \
> backporting of any future patches even riskier.

I would not backport this now. If I understand correctly, at the moment there is not \
intention to introduce FIPS compliance in 1-16 branch.

"""

See the full comment at https://github.com/SSSD/sssd/pull/833#issuecomment-505803985


[Attachment #3 (text/plain)]

_______________________________________________
sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org
To unsubscribe send an email to sssd-devel-leave@lists.fedorahosted.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedorahosted.org/archives/list/sssd-devel@lists.fedorahosted.org


[prev in list] [next in list] [prev in thread] [next in thread]