You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Good catch, thanks! I based #122 on Boulder's PA.WillingToIssue but totally forgot that wildcard support is predicated on PA.WillingToIssueWildcard and should have been considered for Pebble.
cpu
pushed a commit
that referenced
this issue
May 3, 2018
This is a quick fix for the but introduced in PR #122. `*` is not technically a valid DNS character but this commit allows Pebble to treat it as such for a short-term fix to wildcard issuance that was broken in #126.
I believe PR #122 accidentally introduced a bug that now rejects wildcard domain identifiers in new order requests.
pebble/wfe/wfe.go
Lines 767 to 772 in 2462e27
pebble/wfe/wfe.go
Lines 811 to 815 in 2462e27
Should the
*
character be added to the allowed list inisDNSCharacter
?The text was updated successfully, but these errors were encountered: