Re: Registration requests

>> The protocol is different from SSL.
> I'd suggest a less confusing name, then.  Maybe net/ucspi-crypto?  Or
> even net/ucspi/crypto?

 "minssl" has been the "working name" of the project. I could use
another one, if it was as catchy ; "ucspi-crypto" seems a bit...
dull. Granted, it's just silly advertisement business ; find me a
less confusing, but just as striking, name, and I'll happily change. :)


> But I'm guessing minsslserver and minsslclient make tcp connections.
> ucspi-tcp already handles that, so it would be better design to make
> minssl just a filter like recordio or stunnel.

 ... which it is.
 The minssl and minssld programs are UCSPI filters. minsslclient and
minsslserver are actually wrappers: they exec into tcpclient calling
minssl, or tcpserver calling minssld, after some option- and command
line-mangling. If you want to use another UCSPI client and server, just
don't use these wrappers.


> In that case, maybe it would belong in math/.

 minssl, or whatever that is, is not a crypto package. Actually, the
main cryptographic work is done by nistp224 and hash127 :)
(and some trivial implementation of RC4)
 The package is meant to be a networking tool, which shows: UCSPI
interfaces are essentially used in networking environments.

-- 
 Ska