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
I am using quill-magic-url which uses normalize-url (and lets me pass in options through to it).
I am trying to figure out the best way in this setup to prevent homograph attack where a bad user enters something that looks like http://ebаy.com (hover over) but is actually linking to equivalent IDN (punycode): http://xn--eby-7cd.com https://blog.blazeinfosec.com/what-you-see-is-not-what-you-get-when-homographs-attack/
I believe it might be ideal if the browser safe version of normalize-url optionally converted url to ascii format to prevent this.
import punycode from "punycode"; ... if(toASCII) { punycode.toASCII(url); }
Thoughts?
The text was updated successfully, but these errors were encountered:
Add test for #108
e69796d
This package already does this. I added a test to prove it: e69796d
Sorry, something went wrong.
No branches or pull requests
I am using quill-magic-url which uses normalize-url (and lets me pass in options through to it).
I am trying to figure out the best way in this setup to prevent homograph attack where a bad user enters something that looks like http://ebаy.com (hover over) but is actually linking to equivalent IDN (punycode): http://xn--eby-7cd.com
https://blog.blazeinfosec.com/what-you-see-is-not-what-you-get-when-homographs-attack/
I believe it might be ideal if the browser safe version of normalize-url optionally converted url to ascii format to prevent this.
Thoughts?
The text was updated successfully, but these errors were encountered: