[Pkg-gnupg-maint] [SRM] Update of gnupg/gnupg2 to fix a memory leak

[Daniel Leidert]

Am Dienstag, den 16.06.2009, 04:15 -0400 schrieb Eric Dorland:
> * Daniel Leidert (daniel.leidert.spam at gmx.net) wrote:
> > Am Samstag, den 23.05.2009, 17:30 -0400 schrieb Eric Dorland:
> > 
> > [gnupg update for stable]
> > > I didn't see any response to this, did anything come of it?
> > 
> > Hi Eric,
> > 
> > We already uploaded a gnupg update for stable and oldstable. The patches
> > are here:
> > 
> > http://svn.debian.org/wsvn/pkg-gnupg/gnupg/branches/lenny/debian/patches/101_172115_fix_keyring_memory_leak.dpatch
> > http://svn.debian.org/wsvn/pkg-gnupg/gnupg/branches/lenny/debian/patches/101_321871_unset_noecho_on_sigint.dpatch
> > 
> > IMO you can use both for gnupg2 too. As the point releaes date was
> > announced today, you probably have to hurry up a bit, if you want to get
> > these issues fixed for gnupg2 in stable/oldstable too.
> 
> The second patch is not applying well to the version we have in
> lenny. In fact the code has changed enough that I not sure where to
> call the cleanup from. Could someone take a look and give me an
> opinion?

Seems, it was fixed in revision 5022 in upstream SVN with this simple
patch:

> Index: packages/cvs/gnupg_2/g10/signal.c
> ===================================================================
> --- packages/cvs/gnupg_2/g10/signal.c	(Revision 5021)
> +++ packages/cvs/gnupg_2/g10/signal.c	(Revision 5022)
> @@ -81,6 +81,7 @@
>      gcry_control (GCRYCTL_TERM_SECMEM );
>  
>      tty_cleanup_rl_after_signal ();
> +    tty_cleanup_after_signal ();
>  
>      /* Better don't translate these messages. */
>      write(2, "\n", 1 );

Regards, Daniel