On Wed, 18 Nov 2020 11:51, Sirisha Gopigiri said: > But after debugging a little we found that we are running into this > issue only if we use gpg 2.2.4 version. We tested the same code with
You are really using a 3 year old version which was followed by 20 more releases. You also missed 2.2.8 which fixes CVE-2018-12020. > gpg 1.4.20 version and it seems to work fine. I mean we ran the test Same here. If you use 1.4 at all you need to use the latest version (1.4.23 from 2018)! Isn't it a general advise to first thr the latest version of a software if you run into a bug ;-) Anyway, ppl here can in general better help you if you explain your problem in more detail and best show how it can be replicated. For example, I even don't know what this SOPS is and how it used gpg. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
signature.asc
Description: PGP signature
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
