I don't buy it.SECURITY... ;o) Fo tyou AND 2Cows....
I never said or suggested abandoning the Blowfish encryption layer (but I do not trust DES).
--
Mike Allen, 4CheapDomains.Net
[EMAIL PROTECTED]
http://www.4CheapDomains.Net Need Advertising? Try DeerSearch.Com http://www.DeerSearch.com
----- Original Message ----- From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 14, 2003 7:28 PM
Subject: Re: OpenSRS API Question
On Tue, 14 Jan 2003 15:44:16 -0800
"Lynn W. Taylor" <[EMAIL PROTECTED]> wrote:
>Charles,
>
>Your earlier post said that you had an account just for >your own use. That implies very little need for >"integration" into any other application.
EXACTLY!
So why isn't there a *SIMPLE WAY* for me to code the most foundational thing a Tucows account is for: Register a domain name?!
>I would still install the client, and use it to help >decipher the protocols.
Please see my other comments.
>As for "pseudo-" according to the Miriam-Webster it means >"being apparently rather than actually as stated" -- and >gives "SHAM" and "SPURIOUS."
Your being pedantic .....
>So, you are saying that OpenSRS isn't a real registrar, >they just appear to be.
No, I specifically said *I AM* a pseudo-registrar,
1) I *DO NOT* have to genuflect if ICANN looks in my direction
2) I do not have to set up and pay for a 24/7/365 Whois sever who's bandwidth gets used up by a bunch of idiot spammers that mine the whois for email addresses
3) Ahh, I've made my point ....
>-- Lynn
>
>On Tue, 14 Jan 2003 16:34:13 -0600, [EMAIL PROTECTED] >wrote:
>>Lynn,
>>
>>Understood, but I do need to integrate the registration
>>functionality into a unique Windows application I have.
>>Thus PERL or PHP in any form is not possible, period.
>>
>>I have just setup an enom reseller account to carry me
>>though until I have Tucows API running. If only the >>Tucows
>>API was as easy to deal with as enom ..... I suspect the
>>competition will eventually get Tucows to simplify, or
>>better document, their own API but I can't wait for that.
>>
>>"pseudo-registrar" is not an intrinsically negative
>>statement so I honestly have no idea why "everyone at
>>TUCOWS" would take exception to my comment. Perhaps you
>>could explain this statement to me?
>>
>>Thanks!
>>
>>Charles
>>
>>On Tue, 14 Jan 2003 13:55:09 -0800
>> "Lynn W. Taylor" <[EMAIL PROTECTED]> wrote:
>>>Charles,
>>>
>>>I think everyone at TUCOWS would take exception to the
>>>term "pseudo-registrar"....
>>>
>>>If all you want to do is your own registrations, you may
>>>want to take a very hard, serious look at running the
>>>standard PERL client on your Windows box.
>>>
>>>It works just fine, and while the *nix contingent is
>>>usually the most vocal here, there are quite a few of us
>>>running Windows.
>>>
>>>I'm not exactly fluent in Perl, but we've been running
>>>here for a couple of years. It's no hassle.
>>>
>>>-- Lynn
>>>
>>>On Tue, 14 Jan 2003 15:05:09 -0600, [EMAIL PROTECTED]
>>>wrote:
>>>>
>>>>I beleive I understand the handshaking command set, but
>>>>sample can only make my task easier while imposing on you
>>>>even more.
>>>>
>>>>I beleive I have a working Blowfish Encode / Decode
>>>>function and I did see the Dev-List message which
>>>>describes the necessary Private Key "pre-hash". So I'm
>>>>hoping I now just need the actual data to transport and
>>>>parse for results.
>>>>
>>>>Bottom lines,
>>>>
>>>>1) I simply have a personal reseller account with Tucows
>>>>so my needs are extremely simplistic. I use Tucows for
>>>>thier awsome service and the convienance of being a
>>>>pseudo-registrar.
>>>>
>>>>2) I'm a "Widows person" with no available Perl or PHP
>>>>resources. I can't even exchange favors with a Linux
>>>>Buddy. ;-(
>>>>
>>>>3) I have lots of successful Windows network coding
>>>>experiance, so TCPIP coding, etc, should be a non-issue
>>>>for me.
>>>>
>>>>4) All I currently need to do (and for the forseeable
>>>>future) through automation is register new .Info domains.
>>>>If I ever need to do more then I'm betting the API can
>>>>empower me to modify a working .Info "regstration
>>>>system".
>>>>
>>>>5) So I would like the most simplistic and sterile sample
>>>>message(s) / conversation needed to register a new .Info
>>>>domain via the OpenSRS API.
>>>>
>>>>THANK YOU VERY MUCH for your help!
>>>>
>>>>I really do appreciate any and all help you have time to
>>>>provide me with.
>>>>
>>>>Charles
>>>>
>>>>
>>>>On Tue, 14 Jan 2003 11:35:03 -0500
>>>>Colin Viebrock <XXXXX> wrote:
>>>>
>>>>Are you just looking for the .INFO reg command, XML-ized?
>>>>Or do you
>>>>need the entire handshaking command set too?
>>>>
>>>>Appendix A of the API docs is helpful in figuring out the
>>>>XML format,
>>>>and Appendix C explains the handshaking process.*
>>>>
>>>>- Colin
>>>>
>>>>* NOTE: Section 11.2 of the API specification is no
>>>>longer
>>>>valid, and
>>>>should be ignored. Maybe Chuck can get someone at OpenSRS
>>>>to take that
>>>>out of the spec.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>XXXXX wrote:
>>>>
>>>>Tucows support suggested I join this list and ask the
>>>>following:
>>>>
>>>>Can anyone *PLEASE* provide me a sample new (not renew or
>>>>transfer) .INFO domain registration request packet (non
>>>>encrypted of course) which gets sent to OpenSRS server,
>>>>and it's response packet (both success and failure).
>>>>
>>>>Specifically the unencrypted version of the TCPIP packet
>>>>data that gets sent to the port 55000 server. I can then
>>>>us this as my template to perform the registration
>>>>process
>>>>using my own code and reseller ID information (obviously
>>>>your ID information is blank out if the sample packet).
>>>>
>>>>Bottom line is that I have read though the OpenSRS API
>>>>document and, like many such documents, it assumes you
>>>>know what you are doing before you've ever done it --
>>>>Thus
>>>>it's just a referance document. Simply put this document
>>>>would be much more useful if it tied the document
>>>>together
>>>>with 1 or 2 *COMPLETE* send / receive examples. Perhaps
>>>>for something that every reseller is likely to do, like
>>>>register a new domain name .... Ok, I feel better now.
>>>>;-)
>>>>
>>>>Thank you very much in advance for your help!
>>>>
>>>>Charles
>>>>
>>>
>>>
>
>
