M2Crypto: select() behaves weird on SSL sockets

[A.M. Kuchling]

In article <3D04ECED.2030202 at NOSPAMREMOVETHISxs4all.nl>,
	Irmen de Jong wrote:
> Basically, it seems that a SSL socket is no longer in ready
> state when entering select() again, after reading *a part*
> of the available data on the socket.

Perhaps there really is no more data on the socket because OpenSSL has
read it all, but the decrypted data is now sitting in a buffer
somewhere, probably inside an OpenSSL data structure.  

--amk