Summary: | Obvious phishing URLs are not recognized | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Laura David Hurka <laura.stern> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | laura.stern, montel |
Priority: | NOR | ||
Version: | 5.14.2 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Laura David Hurka
2020-06-19 21:05:05 UTC
by default domain can support non ascii char. It will create a lot of false result non ? Some browsers update the address bar to https://kde.xn--rg-emc/. Everything else proceeds as usual. What do you mean with false results? "What do you mean with false results?" if we check each char to compare to no ascii it will signal all utf8 url even if it's not a phishing link. I was thinking that usually URLs are written in their ascii form. If you send a link which is intended to have a non-ascii domain, it will be marked as phishing. Every domain that is actually like höhö.com will be a false positive, but I think these are rare. Of course my idea is to check only the domain name, not the whole URL. |