> Suggestion: instead of separate functions for plain and encrypted
> messages, we should probably let the class keep track of whether
> encryption has been set up, and act accordingly. Trying to send
> plaintext after a session key has been established won't work, nor
> will encrypted traffic without a key.
Agreed. In fact, the only time I read or write unencrypted is during
the "handshaking" process.
> Lookups are also handled *completely* differently than other commands:
> different server and port, and different message format. We'll need
> to take that into account.
I didn't realize this when I started converting the TPP class over to
SRS. I've hacked it a bit to handle that.
You can see my code in progress at:
http://euclid.easydns.com/~cmv/openSRS_base.inc
(This is a snapshot of the code as I am working on it right now, so
expect many changes, and some left-over code from TPP).
Now, if I could just connect to the server, I could test this ... :)
- Colin
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:35:22 EDT