30 Pro
2016
30 Pro
'16
19:24
We are to try out having a few extra national characters
áýúíóæøåð
and in uppercase these are
ÁÝÚÍÓÆØÅÐ
in ccTLD names (.fo)
We found the 'allow_idn' in server.conf
and have it set as 'true' (allow_idn = true),
but this seems not to be enough, and does not really fullfill the requirements.
IDN is mentioned an option in fred, but where/how can we turn this on,
and what should we be aware of ?
...torkil...
31 Pro
31 Pro
0:01
Hi Torkil,
this option actually allows registration of domains in the form of
punycode labels 'xn--*'. So you can register any IDN domain. It's true
that there are some other missing IDN features like character code
checking or bundling of IDN and nonIDN variants. What exactly are the
requirements?
Regards,
Jaromir
On Fri, 2016-12-30 at 18:24 +0000, Torkil Zachariassen wrote:
We are to try out having a few extra national
characters
áýúíóæøåð
and in uppercase these are
ÁÝÚÍÓÆØÅÐ
in ccTLD names (.fo)
We found the 'allow_idn' in server.conf
and have it set as 'true' (allow_idn = true),
but this seems not to be enough, and does not really fullfill the
requirements.
IDN is mentioned an option in fred, but where/how can we turn this
on,
and what should we be aware of ?
...torkil...
_______________________________________________
fred-users mailing list
fred-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/fred-users
1:21
On 30 Dec 2016 23:02, "Jaromir Talir" <jaromir.talir(a)nic.cz> wrote:
What exactly are the requirements?
Well, our board really wants to allow people to register names with faroese
accidentals - described previously.
The customer problem is, that while some names like ámund.joensen.fo
<http://xn--mund-4na.joensen.fo> work perfectly for our customers, names
like joensen.ámund.fo <http://joensen.xn--mund-4na.fo> do not, because of
the 'á'.
The ultimative test would be an acceptance of registering the name
'áýúíóæøåðÁÝÚÍÓÆØÅÐ.fo'. This is to be understood as a string of UTF8
chars, which is equivalent to any upper/lower case combination of the same
UTF8 chars.
In our case, any other non-ASCII chars of UTF8 should be rejected .... I
suppose that we as a ccTLD are authorized to decide on which chars are
acceptable :-)
A short explanation might be that we need to expand the ASCII characters
just a few bits, pr. ccTLD.
Regards Torkil
2:17
Torkil:
The string with accented utf8 characters is a U-Label. You have to
translate it to an A-Label (also called punycode) which is a string
starting with "xn--" and followed by only valis DNS valid characters
(English letters, digits and hyphens).
You can check how it works on https://www.punycoder.com/ (just found it
googling).
Fred will accept xn--mund-4na.fo (which is the punycode for ámund.fo
<http://xn--mund-4na.fo>).
I guess there are idn libraries for most languages so you can translate
back and forth.
---
Mariano Absatz
Enviado desde mi Aifon
On Dec 30, 2016 9:21 PM, "Torkil Zachariassen" <simbulu(a)gmail.com> wrote:
On 30 Dec 2016 23:02, "Jaromir Talir" <jaromir.talir(a)nic.cz> wrote:
What exactly are the requirements?
Well, our board really wants to allow people to register names with faroese
accidentals - described previously.
The customer problem is, that while some names like ámund.joensen.fo
<http://xn--mund-4na.joensen.fo> work perfectly for our customers, names
like joensen.ámund.fo <http://joensen.xn--mund-4na.fo> do not, because of
the 'á'.
The ultimative test would be an acceptance of registering the name
'áýúíóæøåðÁÝÚÍÓÆØÅÐ.fo'. This is to be understood as a string of UTF8
chars, which is equivalent to any upper/lower case combination of the same
UTF8 chars.
In our case, any other non-ASCII chars of UTF8 should be rejected .... I
suppose that we as a ccTLD are authorized to decide on which chars are
acceptable :-)
A short explanation might be that we need to expand the ASCII characters
just a few bits, pr. ccTLD.
Regards Torkil
_______________________________________________
fred-users mailing list
fred-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/fred-users
3 Led
3 Led
20:29
Thank you Mariano for reminding us on the uni/puny-code things.
Yes, fred(client) can create_domain xn--mund-4na.fo and more or less
anything else, given 'allow_idn = true' in /etc/fred/server.conf, all over
EPP, and it goes into the zone file without problems. Even 'ámund.fo
<http://xn--mund-4na.fo>' works as expected in both whois interfaces. This
is great news around here. :-)
Our expectation was that it would be possible to create domain 'ámund.fo
<http://xn--mund-4na.fo>', but this just returns a 'bad format of fqdn
domain'. I guess we will have to adjust our expectations, and just live
with the xn-*.fo domains in lists and such.
This leaves us with the original request which is that we just wanted to
accept a few non-ASCII chars, not the whole UTF8 chebang thing. I guess we
would need to filter user input somehow allowing for a few extra chars. Is
this there currently a solution for this ?
And now for something completely different, but related - which might be
considered a bug:
It seems that in order to register a idn name the registrar has to be a
'system registrar'.
Here is what we get, while being a 'non-system registrar' trying to create
the domain xn-1ca0d.fo
create_domain xn--1ca0d.fo TZ01
Do you really want to send this command to the server? (y/N): y
Return code: 2005
Reason: Parameter value syntax error
ERROR: Element that caused a server error condition: <domain:name
xmlns:domain='http://www.nic.cz/xml/epp/domain-1.4'>xn--1ca0d.fo
</domain:name>
Reason: bad format of fqdn domain
Now we changed the status of the registrar to 'system registrar' and tried
again:
create_domain xn--1ca0d.fo TZ01
Do you really want to send this command to the server? (y/N): y
Return code: 1000
Reason: Command completed successfully
Domain name: xn--1ca0d.fo
Created on: 2017-01-03T18:15:43Z
Expiration date: 2018-01-03
We would expect that others than 'system registrars' should be able to
register idn names, right ?
Btw: /etc/fred/server.conf contains the following two changed idn and epp
settings (as we are still working on getting epp charging to work, but
that's for another day )
allow_idn = true
epp_operations_charging = true
9 Led
9 Led
14:27
On Tue, 2017-01-03 at 19:29 +0000, Torkil Zachariassen wrote:
Thank you Mariano for reminding us on the
uni/puny-code things.
Yes, fred(client) can create_domain xn--mund-4na.fo and more or less
anything else, given 'allow_idn = true' in /etc/fred/server.conf, all
over EPP, and it goes into the zone file without problems. Even
'ámund.fo' works as expected in both whois interfaces. This is great
news around here. :-)
Our expectation was that it would be possible to create domain
'ámund.fo', but this just returns a 'bad format of fqdn domain'. I
guess we will have to adjust our expectations, and just live with the
xn-*.fo domains in lists and such.
This leaves us with the original request which is that we just wanted
to accept a few non-ASCII chars, not the whole UTF8 chebang thing. I
guess we would need to filter user input somehow allowing for a few
extra chars. Is this there currently a solution for this ?
Hi Torkil,
yes, currently we don't do character code checking. I'm trying to find
out some easy way how to do that.
And now for something completely different, but
related - which might
be considered a bug:
It seems that in order to register a idn name the registrar has to
be a 'system registrar'.
Here is what we get, while being a 'non-system registrar' trying to
create the domain xn-1ca0d.fo
Now we changed the status of the registrar to 'system registrar' and
tried again:
We would expect that others than 'system registrars' should be able
to register idn names, right ?
Btw: /etc/fred/server.conf contains the following two changed idn and
epp settings (as we are still working on getting epp charging to
work, but that's for another day )
> allow_idn = true
> epp_operations_charging = true
System registrar can register IDN by default. There is no need to set
allow_idn to true. Don't forget to restart fred-rifd server after
changing /etc/fred/server.conf. Your behavior looks like that your
change actually haven't happened.
Regards,
Jaromir
create_domain xn--1ca0d.fo TZ01
Do you really want to send this command to the
server? (y/N): y
Return code: 2005
Reason: Parameter value syntax error
ERROR: Element that caused a server error condition: <domain:name
xmlns:domain='http://www.nic.cz/xml/epp/domain-1.4'>xn--1ca0d.fo</d
omain:name>;
Reason: bad format of fqdn domain
create_domain xn--1ca0d.fo TZ01
Do you really want to send this command to the
server? (y/N): y
Return code: 1000
Reason: Command completed successfully
Domain name: xn--1ca0d.fo
Created on: 2017-01-03T18:15:43Z
Expiration date: 2018-01-03 _______________________________________________
fred-users mailing list
fred-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/fred-users
12 Led
12 Led
0:34
This leaves us with the original request which is that
we just wanted
to accept a few non-ASCII chars, not the whole UTF8 chebang thing. I
guess we would need to filter user input somehow allowing for a few
extra chars. Is this there currently a solution for this ?
Hi Torkil,
yes, currently we don't do character code checking. I'm trying to find
out some easy way how to do that.
Thanks. We think that the critical step is to handle the EPP
'create_domain' command appropriately serverside.
Assuming the input to be either UTF8 or xn--*, something along this sketcy
lines, might do the trick, in a proper place:
check_tld_name(dn)
TLDCHARS='[áýúíóðæøå]' # from cfgfile
C=[-a-z0-9]+TLDCHARS
D=`idn --ascii2idn dn`
if ( D matches ^[C]+$ )
return true
return false
Your behavior looks like that your
change actually haven't happened
I agree, but don't know how to check it.
13 Led
13 Led
10:17
On Wed, 2017-01-11 at 23:34 +0000, Torkil Zachariassen wrote:
Sure, something like that is needed. We just have to agree on the way
how to configure it in database, what libraries in c++/boost to use for
this check and where to implement it. In new version that we are going
to release in a few weeks we have changed validation mechanism for
domain names on input so it should be now much easier to introduce this
check in future.
You would have to create other non-system registrar and check again
with this registrar. But if you are wrapping FRED with other tool, you
may stay with system registrar.
Regards,
Jaromir
This leaves us
with the original request which is that we just
wanted
to accept a few non-ASCII chars, not the whole
UTF8 chebang thing.
I
guess we would need to filter user input somehow
allowing for a few
extra chars. Is this there currently a solution for this ?
Hi Torkil,
yes, currently we don't do character code checking. I'm trying to
find
out some easy way how to do that.
Thanks. We think that the critical step is to handle the EPP
'create_domain' command appropriately serverside.
Assuming the input to be either UTF8 or xn--*, something along this
sketcy lines, might do the trick, in a proper place:
check_tld_name(dn)
TLDCHARS='[áýúíóðæøå]' # from cfgfile
C=[-a-z0-9]+TLDCHARS
D=`idn --ascii2idn dn`
if ( D matches ^[C]+$ )
return true
return false Your behavior
looks like that your
change actually haven't happened
I agree, but don't know how to check it. _______________________________________________
fred-users mailing list
fred-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/fred-users
2672
days inactive
2686
days old
7 comments
3 participants
participants (3)
-
Jaromir Talir -
Mariano Absatz - gmail -
Torkil Zachariassen