[PYTHON-CRYPTO] Memoryleak in SSL.Connection
reitz at INWORKS.DE
Thu Apr 1 21:04:49 CEST 2004
thanks to all.
On Tue, 30 Mar 2004 23:55:21 +0800
Ng Pheng Siong <ngps at POST1.COM> wrote:
> On Tue, Mar 30, 2004 at 07:25:36PM +1200, Michael Dunstan wrote:
> > I have seen the same leak when running ZServerSSL. Had to restart the
> > server every few days. Until the following change was made for
> > setblocking:
> > - self.send = self.write = self._write_bio
> > + self.send = self.write = Connection._write_bio
> > _ self.recv = self.read = self._read_bio
> > + self.recv = self.read = Connection._read_bio
> > else:
> > - self.send = self.write = self._write_nbio
> > + self.send = self.write = Connection._write_nbio
> > - self.recv = self.read = self._read_nbio
> > + self.recv = self.read = Connection._read_nbio
> > Since applying the patch we have not had any memory problems for some
> > time. About 8 months now.
> Great! Thanks for the patch Michael.
> Now to roll out 0.13p1!
> > It is quite a simple matter to correct the headers used for the image
> > 304's in Zope. There is even an issue in the zope collector about this:
> > http://collector.zope.org/Zope/544. Looks like this incorrect handling
> > of the headers in zope is intentional to support caching in some
> > relic version of apache configured as a proxy server.
> Bad Zope. No biscuit for Zope.
> 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
More information about the python-crypto