Am 10.10.2005, 05:00 Uhr, schrieb felix winkelmann [EMAIL PROTECTED]:
[...]
Do you think it is also sensible to convert things like the tcp-server
egg
into SSL enabled versions?
Hm...I don't know - the tcp-server code is pretty simple - I guess it
would
be not too much work to roll
On 10/10/05, Thomas Chust [EMAIL PROTECTED] wrote:
Maybe we could change the egg in a way that allows connection management
procedures with signatures identical to tcp-(listen|accept) to be
specified, defaulting to the plain tcp ones. One could then specify
something like (cut ssl-listen
On 10/6/05, Thomas Chust [EMAIL PROTECTED] wrote:
another preliminary version of the OpenSSL egg is now available. I fixed
some broken error handling code and added all the certificate loading
routines. The whole thing has undergone some manual testing and seems to
work fine.
The egg is now
Am 05.10.2005, 14:21 Uhr, schrieb Thomas Chust [EMAIL PROTECTED]:
[...]
a preliminary version of my OpenSSL SSL/TLS library bindings for chicken
is available at
http://www.chust.org/projects/openssl.egg
[...]
Documentation for the full interface as it will be (in a few days or so)
Hello,
a preliminary version of my OpenSSL SSL/TLS library bindings for chicken
is available at
http://www.chust.org/projects/openssl.egg
so far only the client side is implemented and verification of peer
certificates is useless, because you cannot load certificate chains, yet.
On 10/5/05, Thomas Chust [EMAIL PROTECTED] wrote:
Hello,
a preliminary version of my OpenSSL SSL/TLS library bindings for chicken
is available at
http://www.chust.org/projects/openssl.egg
Awesome!! I can report that it compiles, and openssl-example.scm runs
fine against my own HTTPS
