> What I have is a bit sketchy (and I'm working on more), but
> you might be interested in
>http://www.darkspell.com/gadgets/ssl Be patient with it: I start w/ a
detailed description of
>how to compose a straight http POST on port 80, then add an SSL connection
on top of that.
>
>(I have code that I'll be posting soon showing a non-blocking client using
the BIOS struct
>talking to a threaded server -- both doing mutual auth, but it's been
promised first to a paying
> print publication.)
>John
>[EMAIL PROTECTED]
>www.darkspell.com
I think this is a great effort, and I'm really appreciative of it.
Two things caught my eye. First, it says that OpenSSL is under the GNU
license, but everything else I've seen indicates it's under a much more
generous open source license.
Second, is there a technical reason for not using the init_client code in
the apps directory for setting up the socket, or is that purely a
pedagogical decision? As an aside, I think it might flow better by treating
the "HTTP using sockets" separately from OpenSSL case, since I expect a fair
number of people (myself included) will start out with a decent
understanding of sockets, and no understanding of SSL.
Thanks again,
Gary
====================================================================
Ready-to-Run Software, Inc.
Software Porting Specialists.
*****************************
Gary Feldman
fax : +1 978 692 9990 Ready-to-Run Software, Inc.
voice: +1 978 692 9922x112 4 Pleasant Street
www : http://www.rtr.com Forge Village, MA. 01886
USA
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
