[PYTHON-CRYPTO] Memoryleak in SSL.Connection

[Andre Reitz]

On Mon, 15 Mar 2004 20:45:19 +0800
Ng Pheng Siong <ngps at netmemetic.com> wrote:

> On Mon, Mar 15, 2004 at 01:24:39PM +0100, Andre Reitz wrote:
> > Perhaps this should be done like this.....
> > 
> >     def setblocking(self,mode):
> >         self.blockingmode=mode
> >     ...
> >     def send(self,...):
> >         if self.blockingmode: return self._write_bio(...)
> >         return self._write_nbio(...)
> > 
> > Does anybody have a better idea?
> 
> Your idea sounds good enough! ;-)
> 
> Does it arrest the leak?
> 

I didnt really try...
courrently I use this as a workaround:

self._connection=M2Crypto.SSL.Connection(...)
....
....
try                  : del self._connection.send
except AttributeError: pass
try                  : del self._connection.recv
except AttributeError: pass
try                  : del self._connection.write
except AttributeError: pass
try                  : del self._connection.read
except AttributeError: pass

this helps....

> -- 
> Ng Pheng Siong <ngps at netmemetic.com> 
> 
> http://firewall.rulemaker.net -+- Firewall Change Management & Version Control
> http://sandbox.rulemaker.net/ngps -+- Open Source Python Crypto & SSL


-- 
__________________________________________________________________________

Als Technologieunternehmen konzipieren und entwickeln wir maßgeschneiderte Feedback- und
Monitoring-Systeme - wie beispielsweise Lösungen für Beschwerde- und Ideenmanagement.
Mit dem Inquery® Survey Server bieten wir eine der leistungsfähigsten Standardlösungen für
Online-Umfragen mit dem Schwerpunkt auf der Messung von Kundenzufriedenheit an.
__________________________________________________________________________


Inworks GmbH
Andre Reitz, Leiter Entwicklung
Hörvelsinger Weg 39, 89081 Ulm, Germany
Tel +49 (0) 731 / 93807-21
Fax +49(0)731/93807-18
Internet: http://www.inworks.de