Re: [SRM] Update of gnupg/gnupg2 to fix a memory leak

To: Daniel Leidert <daniel.leidert.spam@gmx.net>
Cc: debian-release@lists.debian.org, Debian GnuPG-Maintainers <pkg-gnupg-maint@lists.alioth.debian.org>, gnupg2@packages.debian.org
Subject: Re: [SRM] Update of gnupg/gnupg2 to fix a memory leak
From: Luk Claes <luk@debian.org>
Date: Sun, 24 May 2009 19:37:13 +0200
Message-id: <4A1985C9.8010001@debian.org>
In-reply-to: <1241867757.5306.38.camel@leidi>
References: <8faed3c84de783923dd4706e6cfc2e5f.squirrel@webmail.wgdd.de> <200905071903.55292.thijs@debian.org> <1241867757.5306.38.camel@leidi>

Daniel Leidert wrote:
> Hi,
> 
> In the past it had been reported several times, that importing a large
> keyring (for example the Debian keyring) might need a really long time
> and make gnupg allocate much memory (trying to reproduce the issue I
> observed a DoS). I recently reported the issue to Werner Koch and he
> found a memory leak and fixed the issue. It seems the patch applies to
> gnupg (probably to 1.4.6 in oldstable too) as well as gnupg2.
> 
> Should this be fixed in stable and olstable? Then I would prepare the
> packages for gnupg (CCed Eric for gnupg2).

Please upload for stable and oldstable.

Cheers

Luk

Reply to:

Follow-Ups:
- Re: [SRM] Update of gnupg/gnupg2 to fix a memory leak
  - From: Daniel Leidert <daniel.leidert.spam@gmx.net>

References:
- [SRM] Update of gnupg/gnupg2 to fix a memory leak (was: Bug#345911: gnupg: Memory leak fix)
  - From: Daniel Leidert <daniel.leidert.spam@gmx.net>

Prev by Date: Re: support for etchanhalf for how long?
Next by Date: Re: [SRM] Update of gnupg/gnupg2 to fix a memory leak
Previous by thread: Re: [SRM] Update of gnupg/gnupg2 to fix a memory leak (was: Bug#345911: gnupg: Memory leak fix)
Next by thread: Re: [SRM] Update of gnupg/gnupg2 to fix a memory leak
Index(es):
- Date
- Thread