Skip to content

Lint e_qcstatem_qctype_web throws an error for legitimate e-signature and e-seal qualified certificates#1004

Merged
christopher-henderson merged 3 commits into
masterfrom
etsi_serverauth
Nov 22, 2025
Merged

Lint e_qcstatem_qctype_web throws an error for legitimate e-signature and e-seal qualified certificates#1004
christopher-henderson merged 3 commits into
masterfrom
etsi_serverauth

Conversation

@christopher-henderson

@christopher-henderson christopher-henderson commented Nov 16, 2025

Copy link
Copy Markdown
Member

Addresses #1003

The heart of the issue was that this particular lint was using util.IsServerAuth which plays quite fast-and-lose with its definition of what signifies a server auth certificate. Notably, it claims that a certificate with no EKUs at all is a server auth cert. This works well enough for CABF, but it falls on its face in this ETSI lint.

Note that this is the only ETSI lint that makes reference to util.IsServerAuth. So rather than add no util facilities it made sense to make the most simplistic change via a simple util.HasEku call.

"qcSmimeNatural.pem": lint.NA,
"qcSmimeLegal.pem": lint.NA,
"qcLegal.pem": lint.Error,
"qcLegal.pem": lint.NA,

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one stopped reaching its desired error because it did not have the server auth EKU.

@defacto64

Copy link
Copy Markdown
Contributor

This solution seems fine to me.

@christopher-henderson christopher-henderson merged commit d96b640 into master Nov 22, 2025
8 checks passed
@christopher-henderson christopher-henderson deleted the etsi_serverauth branch November 22, 2025 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants