Open 389-ds-bot opened 4 years ago
Comment from mreynolds (@mreynolds389) at 2019-02-07 17:56:29
Metadata Update from @mreynolds389:
Comment from firstyear (@Firstyear) at 2019-10-23 04:20:46
@kenoh Is this covered by system TLS policy now? And do we use it?
Comment from firstyear (@Firstyear) at 2019-10-23 04:21:35
@kenoh Is this covered by system TLS policy now? And do we use it?
Comment from firstyear (@Firstyear) at 2019-10-23 04:22:04
Okay, I commented on the wrong ticket but I can't delete them. RIP.
Comment from mreynolds (@mreynolds389) at 2020-02-26 16:51:11
Metadata Update from @mreynolds389:
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/50150
Currently the NssSsl class is using hardcoded issuer data when creating nss db, self signed CA etc. We need to be allowed to insert custom issuer data, because we have to automate a case, where we are testing processing of issuer that has comma in it's name (or presumably other characters that require escaping).