Hi, in the master branch there is the commit
https://dev.gnupg.org/rG926d07c5fa05de05caef3a72b6fe156606ac0549 from September 2017 for configure.ac that allows to circumvent a huge performance regression with gnupg v2 keys in some contexts. This commit is not in stable though. I am not familiar with the process how commits get selected for inclusion into the stable branch. Is there a chance that it will make it into gnupg stable anytime soon? Thanks Felix To recall: This issue applies to contexts like gnupg being called internally by postgresql where there is no agent, so the security calibration / delay of 100 MESC is applied to every single decryption call. Refer to my original posting and the explanation by Werner Koch, proposing to reduce MSEC at compile time: https://lists.gnupg.org/pipermail/gnupg-users/2018-September/060999.html _______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
