Timeline for Why are SSL CAs prohibiting double dash in third and fourth characters?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 22, 2021 at 18:11 | comment | added | Patrick Mevzek |
@GACy20 No, it is not prefix-- that is disallowed. It is pattern ^..-- (except if xn--) which is only two characters at start then 2 dashes. A starting dash is also disallowed, per other rules.
|
|
| Dec 22, 2021 at 7:32 | comment | added | GACy20 |
@MechMK1 As mentioned by EricLaw answer if you allow any string then you cannot use <prefix>-- as an extension mechanism for future extensions anymore. In other words the standard says that <prefix>-- is a reserved combination, currently <prefix> can only be xn to mean the punycode extension, but in the future other might exists. Allowing other domains means in the future their interpretation might suddenly change which is not good.
|
|
| Dec 21, 2021 at 22:20 | comment | added | user163495 |
That doesn't really explain a lot. What specifically is the issue with allowing --?
|
|
| Dec 21, 2021 at 21:45 | history | answered | dcom-launch | CC BY-SA 4.0 |