Re: opensrs errors for multilingual domains

[GaGaDomain]

I don't know what you mean by "minor" issue.. but after no answers except asking us to send what we inputed into our cgi from support i tried tracking down the problem myself, and now have somewhat an idea what the problem is(was??)   first of even if all the contact info is all < 127 ASCII this problem occured when our customers tried registering domains with a previous profile being a multilingual domain. (i sent this info to support) b.t.w. we know this because we log all(except password info) cgi input and output through our reg_system.cgi   this, in my opinion is a bug whichever way you look at it, and should be fixed pronto, maybe already fixed?   note: we have never allowed non-english characters in our contact info when registering domains as we have always feared it would cause problems in the future   second of all, after analyzing opensrs reg_system.cgi, we found out that the CGI automatically sends all form input to opensrs, which means if we create a new field for cc processing and put korean characters in it, like the domain name, opensrs spits out an error. it used to NOT(spit out the error) do that before opensrs servers moved   personally i think it is real bad security that all form input is automatically parsed and sent off to opensrs as this is asking for hackers to try to screw up opensrs resellers by sending  manipulated form values. not sure but i think i noticed a "security" change in the source from 2.41 to 2.46 because of this behavior.   I would appreciate a reply whether the first is fixed and whether the second has changed.. that being non opensrs fields being screened for non < 127 ASCII characters.   lastly i am VERY INTERESTED in knowing if the opensrs codebase is going to complety move to the opensrs-sf code or if the current code is going to be developed together in parallel. personally i like the current style of coding compared to opensrs-sf. support once told me it's opensrs-sf is going to replace the current code, and now i hear not so sure.   thanks, GaGaDomain Park Yong Gu (mail: [EMAIL PROTECTED] MSN ID: [EMAIL PROTECTED]) ----- Original Message ----- From: CharlesDaminato To: 박용구 Sent: Saturday, January 05, 2002 1:31 AM Subject: RE: opensrs errors for multilingual domains Actually, we have tracked down a minor issue that occured as a component of the move, and are working to solve this issue. We will advise. Charles Daminato OpenSRS Product Manager Tucows Inc. - [EMAIL PROTECTED] > -----Original Message----- > From:     > [mailto:[EMAIL PROTECTED]]On Behalf Of Jose Luis Moya > Sent: January 4, 2002 11:07 AM > To: discuss-list > Cc: Horacio > Subject: Re: opensrs errors for multilingual domains > > > We have nearly the the same problem, and also at manage, with domains > already registered. > My question is what are we suppose to do with domains that are already > registered and have invalid characters in the contact details. How can we > not use complete character set in city name or country? > > Thanks. > > Jose Luis Moya > > > > > From: "Charles Daminato" <[EMAIL PROTECTED]> > > Date: Wed, 2 Jan 2002 13:07:55 -0500 > > To: "???" <[EMAIL PROTECTED]>, "discuss-list" > <[EMAIL PROTECTED]> > > Subject: RE: opensrs errors for multilingual domains > > > > This will happen if you have multilingual characters in the contact > > information; the XML system we use does not allow for high (>127) ASCII > > characters (and has not since Sept 2000) unless you use the old > (deprecated) > > API (which does not support multilingual names). Apologies; > we're looking > > for a way around this. > > > > Charles Daminato > > OpenSRS Product Manager > > Tucows Inc. - [EMAIL PROTECTED] > > > >> -----Original Message----- > >> From: [EMAIL PROTECTED] > >> [mailto:[EMAIL PROTECTED]]On Behalf Of ??? > >> Sent: December 27, 2001 7:13 AM > >> To: discuss-list > >> Subject: opensrs errors for multilingual domains > >> > >> > >> support isn't answering because it's holiday season so this is > >> causing many problems :( > >> > >> we are getting errors registering multilingual domain > >> registrations after your servers moved... we were registering > >> korean domains(UTF-8) without any problems before your servers > >> moved, but after your servers moved we have not been able to > >> register any domains through our cgi, which has NOT changed. no > >> upgrades have been done to our server. > >> > >> this is the error we keep getting: Invalid XML or unsupported > >> high-end ASCII > >> > >> please look into this carefully as we can register domains > >> through the reseller interface fine but NOT through our cgi, > >> which has not been modified in any way, nor has it's > >> environment(server, perl, web server software, etc) > > > > >