[RFC PATCH] enable configurable SECMEM_BUFFER_SIZE

Shah, Amul Amul.Shah at fisglobal.com
Tue Nov 28 12:14:21 CET 2017

>thanks for your persistence on this, i'm glad to see new ideas and approaches
>are being tried out.  You're not the only person who has run into concurrency
>problems with gpg-agent.

[amul:4] Thanks for the kind words.

>On Fri 2017-11-24 10:30:48 +0000, Shah, Amul wrote:
>> [amul:3] DKG, What does one need to do to back-port these changes to stable?
>> File a bug, attach patches that apply cleanly to the target sources
>> and request the maintainer to add them?
>Are you asking about debian stable, or the GnuPG stable branch?  Since you're
>asking me specifically, i assume you're asking about debian stable (aka
>"stretch").  please ignore the rest of this if that isn't what you meant ;)

[amul:4] Ack! I did mean Debian stable.

>At first glance, it looks like it would require patches to libgcrypt itself,
>in addition to patches to GnuPG.
>That would be something to coordinate for a point release perhaps, but it
>could be complicated; there are several other bugfix improvements that it
>would also be good to include into debian stable.

[amul:4] If I understood Werner's last mail, Debian stable should update to
libgcrypt 1.8.1 and then back port his changes to GnuPG 2.1.

>To make this stand out clearly, you probably want to start by opening a bug
>report (in the debian BTS) against the gcrypt package, tagged appropriately
>for the affected versions, explaining the problem, pointing to the upstream
>reports and commits, and also mark it so that it "affects" the gnupg2 source

[amul:4] I created #882985 for this issue. I ran reportbug from my Debian
"unstable" server, and since this is my first time through the utility, I'm
sure that I made more than one mistake.

[amul:4] I'm not sure if I set the "affects" gnupg2 correctly.

The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.

More information about the Gnupg-devel mailing list