Skip to content

Stop generating CN fields #18

@njsmith

Description

@njsmith

Right now we throw some nonsense in the CN field and put the good stuff in the SAN, on the theory that this will help catch any old software that's incorrectly relying on the CN field instead of SAN. But this violates the CABF baseline requirements. We should leave the CN out entirely, which will let us catch broken software while also meeting the requirements.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions