>> Soo... Given we prefer to stay conservative and not change SSSD crypto
>
> I didn't say that!
I know, I'm not saying that you took a decision on that but I was
speaking in plural form as I recognize what you say in the sense that
indeed there may be cases which we don't think of that we could
On Wed, Dec 02, 2020 at 03:29:43AM -, Marco Trevisan (Treviño) wrote:
> Soo... Given we prefer to stay conservative and not change SSSD crypto
I didn't say that!
> backend fully (to be clear, I would have preferred it to follow
> upstream, not to provide a solution that will change in next
Soo... Given we prefer to stay conservative and not change SSSD crypto
backend fully (to be clear, I would have preferred it to follow
upstream, not to provide a solution that will change in next LTS no
matter what, and avoid having "frankensteins", but wasn't a strong
requirement for me) I've
** Summary changed:
- Recompile SSSD in 20.04 using OpenSSL (instead of NSS) support
+ Recompile SSSD in 20.04 using OpenSSL (instead of NSS) support for p11_child
** Description changed:
[ Impact ]
SSSD supports in 20.04 two security backends: NSS and OpenSSL
(speaking in past tense
