search

SSLMate / caa_helper

Generate a CAA policy
https://sslmate.com/caa/
Mozilla Public License 2.0
152 stars 35 forks source link

Symantec wildcard checkbox is broken #37

Closed dragongeek closed 7 years ago

dragongeek commented 7 years ago

When I click other providers wildcard checkbox, it adds the wildcard entry, but clicking Symantec it removes any wildcard entries, even for other organizations. (I clicked both with and without wildcard for Symantec and Digicert in my test). I'm particularly interested in the RFC 3597 syntax, since I need both, but that is unreadable to me.

AGWA commented 7 years ago

Hi @dragongeek, I am unable to reproduce this.

Note that if the set of wildcard CAs matches the set of non-wlldcard CAs exactly, then the CAA spec allows the issuewild property to be omitted (instead, the issue properties will be consulted for wildcard issuance). Is this the behavior you were seeing?

dragongeek commented 7 years ago

Only if I just had Symantec checked. If I check both symantec and digicert, all boxes, only symantec shows up with an issue and issuewild. digicert does not show up with an issue statement.

AGWA commented 7 years ago

I'm having trouble following which boxes you are checking. Could you provide a screenshot of the page so I can tell for sure? Also, what browser are you using?

dragongeek commented 7 years ago

checked_settings

dragongeek commented 7 years ago

I don't know if something was updated, but today when I check all the boxes, as in above image, the output is consistent. Problem appears to be solved. output_today