Alexander Scheel

Thanks @FiloSottile for the pointers! Reading that after reading the cert spec format again makes sense to me how that'd work.

@kitography @stevendpclark -- updated!

A few follow-up minor changes can be merged in the next PR. Thank you @Gabrielopesantos for kicking this off and doing a lot of the work in this PR!!

This keeps getting more interesting... :-) Can you share _just_ the ASN.1 of that constraint? If you run something like this: OpenSSL command to parse ASN1 structure ``` $ openssl...

Yep, the earlier Go issue I linked is correct and is the root cause of this behavior. You've got a [boolean with value `0x01`](https://lapo.it/asn1js/#MAMBAf8) which is fine according to BER...

I think SUSE ships podman and prefers it over Docker like Red Hat does, but no, this is mostly from my own personal choices (and that I run on a...

As 1.12 has been branched, I feel good merging this now. Thank you @greut!

OK so this approach isn't viable right now. We'd need to update certmonger to read and respect nonces (and eventually Tomcat CSRF tokens) before this'd work. @rcritten -- we're thinking...

@evgenyz said: > @cipherboy the `content` tag is for problems related to the security content rather than the scanner itself. As far as I can see it is not the...

@jan-cerny I was debating that as well. IIRC we only merged the portion of this related to the scan results. You mentioned on the PR: > 1. It would be...