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
Hi, I got an BadDER error when use rust-tls to build non-web tls application.
After investigation. I found the cause of BadDER is the DNS name *.b is not valid.
// Like NSS, require at least two labels to follow the wildcard label.
// TODO: Allow the TrustDomain to control this on a per-eTLD+1 basis,
// similar to Chromium. Even then, it might be better to still enforce
// that there are at least two labels after the wildcard.
if label_count < 3{
May I know why it had this check or based on what specification?
Because I'm not the one who generate this certificate. if the DNS name is illegal or it has security issue, I think I need some evidence to convince others.
Thks
The text was updated successfully, but these errors were encountered:
And it seems a little strange.
When I put the illegal DNS name after the legal DNS name in my test env. it works. but it doesn't work if I change the order.
Hi, I got an
BadDER
error when userust-tls
to build non-web tls application.After investigation. I found the cause of
BadDER
is the DNS name*.b
is not valid.I've tried some format.
After check the code, I found it's was intentional.
webpki/src/name/dns_name.rs
Lines 568 to 572 in b481381
May I know why it had this check or based on what specification?
Because I'm not the one who generate this certificate. if the DNS name is illegal or it has security issue, I think I need some evidence to convince others.
Thks
The text was updated successfully, but these errors were encountered: