Actually xn--example.com doesn't decode to example.com because in the
absence of a "-" separator "example" would be treated as encoded
non-ascii characters.
This means that it's impossible to encode an ASCII domain as an IDN
because each decoded label has to encode back to the original.
On 30
>Actually xn--example.com doesn't decode to example.com because in the
>absence of a "-" separator "example" would be treated as encoded
>non-ascii characters.
>
>This means that it's impossible to encode an ASCII domain as an IDN
>because each decoded label has to encode back to the origina
On Fri, 28 Apr 2017 15:57:16 +0100
RW wrote:
> > >if idn decode gives 7bit domain hostname, its a fake domain
> >
> If he meant something like
>
>xn--example.com
>
> it seems unlikely that *any* registrar would allow that to be
> registered as an ordinary ascii domain.
Actually xn
On 4/28/2017 4:56 AM, Matus UHLAR - fantomas wrote:
On 22.04.17 00:37, Benny Pedersen wrote:
https://www.xudongz.com/blog/2017/idn-phishing/
should we care in spammassassin ?
yes.
i ask since its solved in chrome, but its entirely a bad nic tld
handling on that isssue
if idn decode gives
On 4/28/2017 10:57 AM, RW wrote:
it seems unlikely that*any* registrar would allow that to be
registered as an ordinary ascii domain.
The question to me is do they? If they do, it's a legit domain and not
really up to us to judge them unless it shows signs of fraud...
On Fri, 28 Apr 2017 10:56:45 +0200
Matus UHLAR - fantomas wrote:
> On 22.04.17 00:37, Benny Pedersen wrote:
> >https://www.xudongz.com/blog/2017/idn-phishing/
> >
> >should we care in spammassassin ?
>
> yes.
>
> >i ask since its solved in chrome, but its
On 4/28/2017 4:56 AM, Matus UHLAR - fantomas wrote:
On 22.04.17 00:37, Benny Pedersen wrote:
https://www.xudongz.com/blog/2017/idn-phishing/
should we care in spammassassin ?
yes.
i ask since its solved in chrome, but its entirely a bad nic tld
handling on that isssue
if idn decode gives
On 22.04.17 00:37, Benny Pedersen wrote:
https://www.xudongz.com/blog/2017/idn-phishing/
should we care in spammassassin ?
yes.
i ask since its solved in chrome, but its entirely a bad nic tld
handling on that isssue
if idn decode gives 7bit domain hostname, its a fake domain
agreed
https://www.xudongz.com/blog/2017/idn-phishing/
should we care in spammassassin ?
i ask since its solved in chrome, but its entirely a bad nic tld
handling on that isssue
if idn decode gives 7bit domain hostname, its a fake domain
