[PYTHON-CRYPTO] Some issues with M2Crypto 0.18 and timeouts

[Jesus Cea]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jesus Cea wrote:
> Definitively M2Crypto, as is, is not suitable for server SSL, since DoS
> (Denial of Service) is trivial :-(, unless the programmer fight the BIO
> layer, hard.

I'm learning more about openssl internals that I would like to know :-).

Seems "accept_ssl()" can be called several times if the socket is
notblocking. Nice. But return codes is not consistent with openssl docs.
In fact, I can't make sense of it :-?. Any example out there?. I can't
differenciate between "waiting for read" and "waiting for writing", so I
can't use a "select" there. Any idea?.

I just discovered the undocumented "Connection._write_nbio()" and
"Connection._read_nbio()". Could I use them combined with a "select()"
loop?. Seems so, actually.

- --
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea at argo.es http://www.argo.es/~jcea/ _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea at jabber.org         _/_/    _/_/          _/_/_/_/_/
                               _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBRwPcCJlgi5GaxT1NAQLAwAP/X1nJL1Hf3x5KKNsnvG15sf24CabbDAc/
9t8PQnnRTSZql0nbvOxY+bBeMnZJCjNHFgpB4xf45twMilxv3uWQUA0IbwV3wRjO
khJGQ5UQ0MNEW67Z3LssvF4shxLElRxqzA+Rk30IFImYHrpH5i77haLXPLhT0DOo
I1RqYMAqpg8=
=3VAl
-----END PGP SIGNATURE-----