We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
n
As mentioned in publicsuffix/list#1872 (comment)
Multiple psl libraries share the same bug while handling wildcards.
psl
I went over all the FOSS implementations in https://publicsuffix.org/learn/ , and I found 3 of them behave funny for wildcard domains. In particular: regdom-libs publicsuffix2 publicsuffixlist.js Seems to all mislabel eTLD-n x [eTLD minus n] (with n from 0 to infinite), as an eTLD, if another eTLD y is defined as a subdomain of that x eTLD-n. As an example publicsuffix2 behaviour with the following patch: // Linode : https://linode.com // Submitted by <security@linode.com> members.linode.com -nodebalancer.linode.com +*.nodebalancer.linode.com +*.linodeobjects.com +ip.linodeusercontent.com
I went over all the FOSS implementations in https://publicsuffix.org/learn/ , and I found 3 of them behave funny for wildcard domains. In particular:
wildcard
Seems to all mislabel eTLD-n x [eTLD minus n] (with n from 0 to infinite), as an eTLD, if another eTLD y is defined as a subdomain of that x eTLD-n.
x
0
infinite
y
As an example publicsuffix2 behaviour with the following patch:
publicsuffix2
// Linode : https://linode.com // Submitted by <security@linode.com> members.linode.com -nodebalancer.linode.com +*.nodebalancer.linode.com +*.linodeobjects.com +ip.linodeusercontent.com
Example here:
This bug has already been reported in this library here
The text was updated successfully, but these errors were encountered:
Thanks!
Sorry, something went wrong.
No branches or pull requests
As mentioned in publicsuffix/list#1872 (comment)
Multiple
psl
libraries share the same bug while handling wildcards.Example here:
This bug has already been reported in this library here
The text was updated successfully, but these errors were encountered: