13 Jan
2017
13 Jan
'17
10:17 a.m.
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