FF Desktop shows xn–eepass-vbb[.]info for me. (Edit: Was just told on HN that I have a non-default flag, in about:config set network.IDN_show_punycode to true if you want this behavior)
FF Android redirects me to the real keepass page and I have no idea why :D
This should be ON by default, in my opinion. Also, I believe Mozilla has a massive opportunity here to demarcate themselves as the more security-conscious browser vendor. “This phishing trick works on all major browsers except Firefox” would be great publicity material.
Not that easy, imo. I’m pretty sure there are countries, especially with non-latin alphabets, who regularly use IDNs.
edit: Including Germany, where FF on Desktop is still a mainstream browser at around 20% (and I’d bet FF gets regularly undercounted because FF users are more likely to block trackers).
They could add some kind of warning message that notifies you when the URL has unicode in it. Then the user can decide if they want to disable the warning or not.
That’s true. Also I guess domain names in most ideogram-based languages cannot be meaningfully converted to ASCII. The best detection method I’m aware of is detecting a mix of different alphabets in the domain, but I imagine even this has a lot of false positives
Turning it on by default would be a massive disservice to the work that domain registries and registrars have been doing to allow Unicode to be used in domain names. In Spanish speaking countries the ñ character is pretty ubiquitous for example, and the workaround of replacing it with an n creates many problems like misdirected web traffic and typos in email addresses. Unicode in URLs and domain names is a feature, abuse should be attacked by means other than disabling it.
FF Desktop shows xn–eepass-vbb[.]info for me. (Edit: Was just told on HN that I have a non-default flag, in
about:configsetnetwork.IDN_show_punycodetotrueif you want this behavior)FF Android redirects me to the real keepass page and I have no idea why :D
Just enabled this, thanks!
Lol are you sure?
deleted by creator
deleted by creator
This should be ON by default, in my opinion. Also, I believe Mozilla has a massive opportunity here to demarcate themselves as the more security-conscious browser vendor. “This phishing trick works on all major browsers except Firefox” would be great publicity material.
Not that easy, imo. I’m pretty sure there are countries, especially with non-latin alphabets, who regularly use IDNs.
edit: Including Germany, where FF on Desktop is still a mainstream browser at around 20% (and I’d bet FF gets regularly undercounted because FF users are more likely to block trackers).
They could add some kind of warning message that notifies you when the URL has unicode in it. Then the user can decide if they want to disable the warning or not.
That’s true. Also I guess domain names in most ideogram-based languages cannot be meaningfully converted to ASCII. The best detection method I’m aware of is detecting a mix of different alphabets in the domain, but I imagine even this has a lot of false positives
Turning it on by default would be a massive disservice to the work that domain registries and registrars have been doing to allow Unicode to be used in domain names. In Spanish speaking countries the ñ character is pretty ubiquitous for example, and the workaround of replacing it with an n creates many problems like misdirected web traffic and typos in email addresses. Unicode in URLs and domain names is a feature, abuse should be attacked by means other than disabling it.
Seems to be on by default in Librewolf(I just checked mine from the AUR on Arch), maybe consider that one!