-
Notifications
You must be signed in to change notification settings - Fork 769
Description
OPNsense version: v25.7.11_2
os-acme-client version: v4.11
Hello!
Using the ACME Client plugin I encountered a minor issue on the following page:
Services -> ACME Client -> Accounts
/ui/acmeclient/accounts
When creating or modifying an ACME account, the maximum length for an email address is too small.
The email specification states a maximum length of 254.
(It's a bit of a rabbit hole, here is the related Stackoverflow question for those interested)
However, after a bit of testing, it seems like the current limit for the input field is:
[Max 64 chars] @ [Max 63 chars] . [Max 63 chars]
The above means that all 3 parts of the address are checked separately, and if more than 64 chars long, then the email address field is considered invalid.
The following is the longest email address I could assign with the current version (64a @ 63b . 63c)
Adding a single character to any part of the address would make it invalid.
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa@bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb.ccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc
The request:
Make the email address field accept emails up to 254 characters long.
(Or if you want to "be safe", a little bit lower, like 250 or 240 characters is also acceptable.)
Reason:
While commonly used bob@example.com email addresses are usually very short, but for automatically generated "throwaway" email addresses even 200+ characters is still somewhat reasonable and well-within specs.
For example, the following address is 187 characters long: acme-contact-for-lets-encrypt-[generated 100 char long random string]+tag-for-some-other-system@long-name-facility.example.com
(With the "original" acme.sh script on a Debian system I already registered and using Let's Encrypt accounts with an email address length of 140 chars, so both Let's Encrypt and acme.sh support long email addresses)