Skip to content

security/acme-client: always use configured cert name in cert description#5282

Open
pgerber wants to merge 1 commit intoopnsense:masterfrom
pgerber:common-name
Open

security/acme-client: always use configured cert name in cert description#5282
pgerber wants to merge 1 commit intoopnsense:masterfrom
pgerber:common-name

Conversation

@pgerber
Copy link

@pgerber pgerber commented Mar 2, 2026

Important notices
Before you submit a pull request, we ask you kindly to acknowledge the following:

If AI was used, please disclose:

n/a


Related issue
n/a


Describe the problem
A PHP warning is triggered.


Describe the proposed solution

See commit message.


…tion

This a fix for the PHP warning below. I propose to simply never use the
certificate name because:

a) It's easier to understand if the description always has the same source.

b) The use of a common name is no longer recommended and will disappear
   sooner or later anyway [1,2].

[1]: https://letsencrypt.org/docs/glossary/#def-CN
[2]: https://letsencrypt.org/docs/profiles/#tlsserver

Related PHP warning:

[02-Mar-2026 15:02:54 Etc/UTC] PHP Warning:  Undefined array key "commonname" in /usr/local/opnsense/mvc/app/library/OPNsense/AcmeClient/LeCertificate.php on line 206
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant