If you are wondering about the private keys, you get them at resellers-test.opensrs.net or resellers.opensrs.net, there is option to generate them.
mayo > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Mayo > Sent: February 12, 2002 11:46 AM > To: [EMAIL PROTECTED] > Subject: RE: DES IV > > > Hi Chris, > > The messages you sent just got to the mailing list. Here's my > feedback. > If you find anything offending, my apologies, I have no > intensions to do > that. > > > Sent: Sunday, February 10, 2002 12:38 PM > > To: '[EMAIL PROTECTED]' > > Subject: RE: DES IV > > > > > > Well after wasting the weekend on this, I am just going to give up > > again. So that makes for over a year trying to wasde through > > these long > > documents only to find they do not help AT ALL in developing > > a client to > > interface to the OPENSRS system. > > The docs are quite useful, and if you search around, there has been > number of opensrs clients developed already, such as > OpenSRS-PHP (which > is backend for communication with server) and I successfully built > front-end (it's partly still in works, but it works great) > for it, with > no troubles at all. > > > The document you refered me too only has made things worse, I > > think. I > > am trying to use DES, the document is for Blowfish. But it > > does help me > > know that the PDF's posted on the OPENSRS site are even > more worthless > > than I thought. The system obvisouly has many unpublished and > > proprietary routines in it that no one seems to understand. > > Charles said they recommend Blowfish. "BTW - our suggestion > is that you > use Blowfish, it's faster, stronger encryption." and that's > why he gave > you docs for Blowfish. > > All of the routines are in the docs, and if you look at the client > (reg_system.cgi and manage.cgi) it is not using any more > calls than the > docs have. > > > Why can't the test server actually return some sort of error code or > > provide a test interface to see if we are on the right track? Just > > dropping us off is SOOOOO frustrating. > > The server returns error code all the time (at least in my > experiences). > Most likely your routines for sending and receiving data do not work > properly. > > > I am getting to the checksum and then trying to send the > MD5 'digest' > > back. I try to encrypt it using DES, sending the server the DES > > encrypted block using the key I generated. So I asked about it last > > week and got a little help from Charles and one of the > OPENSRS staff. > > What perplexes me is that neither one seems to understand the > > encryption > > parts of the system, which is the hard part of the whole > > process. This > > is troubling to me. > > The OpenSRS-PHP works perfectly with both DES and Blowfish. > If you can't > solve the authentication problem, you may want to look at the Perl or > PHP code to see how it is done there. Also, you should first send your > version to server and await version reply from the server, and > authenticate directly after that. I'm not sure, but I think the server > will not talk to you if you don't send it version or the > authentication > is incorrect. > > > What I do find out from Charles' reply is that there are many things > > going on in the encryption process and obvisouly what works > > for Blowfish > > does not work for DES. These are public symetric encryption > > methods. I > > went through and evaluated many articles and sample code to > > come to the > > conclusion that this is not a public interface and PERL is > > simply not an > > acceptable language for us and many others to work with. > > Again, there is a quite a few OpenSRS clients around. The Perl one is > not the one and only. > > > So with all this said and much venting included. Please > DOCUMENT the > > system properly so that we may right clients for our sites and > > management software to that we can properly promote domain > > registration. > > There is few errors in the documents, but not any severe ones that a > programmer couldn't deal with. I have found the docs quite helpful and > used them all the way. > > > Thanks for bearing with my frustration and I just hope this > > will finally > > help me get this stuff completed. I have spent many > weekends over the > > past year trying to figure this stuff out. > > If you get cut-off from the server or don't receive errors at all, you > may want to check out the routines that encode all the data into XML, > and parse all the data from XML, as well as the routines that > communicate with the server. > > > Chris Love > > > > Extreme Web Works > > > > www.extremewebworks.com > > > > 919-836-0998 > > I'll be glad to help if I can be of any assistance. > > mayo > >
