And This one
Chris Love Extreme Web Works www.extremewebworks.com 919-836-0998 -----Original Message----- From: Chris Love [mailto:[EMAIL PROTECTED]] Sent: Monday, February 11, 2002 3:11 PM To: '[EMAIL PROTECTED]' Subject: DES encryption I am still trying to find someone who can answer these questions. Evidently when it comes to encryption you guys clam up. Since neither one of my post yesterday to the development list have been posted I will include them here and hope you will provide the nessecary help and documentation. _________________________________ 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 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. 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. 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. 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 publ ic 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. 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. 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. __________________________________________________________ Well I guess my earlier message is not going to be posted or responded to, but these are some of my findings. As I compare what I have developed and compare it to the PHP, Java and Perl Clients I can find no difference in what I am doing except that I want to use DES. What I am noticing from the server is, well, disturbing. I can do consecutive runs through the handshake and receive multiple responses. Examples: Run 1- 1)Connect 2)Read Check Version 3)Send Version Check Reply 4)Send Authenticate 5)Receive Check Version 6).........Nothing really matters anymore because the sever farted Run 2- 1)Connect 2)Read Check Version 3)Send Version Check Reply 4)Send Authenticate 5)Receive Challenge (encouraging) 6a)Create MD5 Hash of Challenge bits (16 bytes long) 6b)Let's try to encrypt that HASH 6b1)MD5 Hash the Key 'Seed' and get the first 8 bytes for the real DES key 6b2)get the first second 8 bytes for the real DES IV (I think this could be anything) 6c)DES Encrypt the Challenge Bits 6d)change the encrypted bytes to ASCII 6e)Add 'RandomIV' and the IV before the encrypted String 6f)Send the Encrypted Bytes back to the OPENSRS Server 7)Death Run 2- 1)Connect 2)Read Check Version 3)Send Version Check Reply 4)Send Authenticate 5)Receive Challenge (encouraging) 6a)Create MD5 Hash of Challenge bits (16 bytes long) 6b)Let's try to encrypt that HASH 6b1)MD5 Hash the Key 'Seed' and get the first 8 bytes for the real DES key 6b2)get the first second 8 bytes for the real DES IV (I think this could be anything) 6c)DES Encrypt the Challenge Bits 6d)change the encrypted bytes to ASCII 6e)Add 'RandomIV' and the IV before the encrypted String 6f)Send the Encrypted Bytes back to the OPENSRS Server 7)Receive another Challenge request??????? 8)OK what now?????????? This is what is happening to me. I need help with what I am doing wrong.
