Skip to content

Use Custom RootCertificate, DefaultWindows And BouncyCastle has Two behaviors? #965

Description

@kingcomxu

when set CertificateEngine = DefaultWindows, every thing fine,
and when set CertificateEngine = BouncyCastle, browser shows ERR_CERT_AUTHORITY_INVALID!!!

In BCCertificateMaker.cs source ,
var issuerDn = new X509Name(issuerName);
I change it to
var issuerDn = new X509Name(true, issuerName);
Then everything is fine.

ps: my root.pfx is created by openssl, and used in filldercore is worked, so I think maybe it's a bug in BCCertificateMaker

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions