The protocol is essentially binary. If you'll look more carefully at
the perl scripts, you'll see that a packed 16bit integer must come
before any command, data, etc. This integer tells the client/server how
much data to expect before processing the command. The protocol itself
is very simple, but the issue is getting encryption working. I know
that bboy@bboy.com has build a library in C that properly communicates
with the server over an encrypted channel (I think he's using libdes).
I've tried doing the same thing using PHP and libmcrypt with no
success. I did have a completely functional client going without
encryption, but don't know if it would work with the current system.
Brad
>
> |> I'm having more basic problems than
> |> that, even. From looking at the perl scripts I have, it seems that
> |> encryption is optional. I tried telnetting to the server and it
> |> answered, but then it would not respond to anything I typed. For
> |> example, I tried telling it:
>
> My understanding is that the unencrypted verison no longer works on
> rr-n1-tor, though it might on horizon.
>
> That said, I am also unable to get past the 'OpenSRS SERVER 3.0: READY'
> prompt on port 50000 using nc(1). I've no idea why. I did it from
> the host my instance of the client scripts runs on, so that is not
> the problem. I also tried various line endings. No help there.
>
> With luck tomorrow's release will prove helpful in diagnosing this.
>
> -JimC
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:35:22 EDT