Hello Werner, Thank you for your reply and apologizes for my slow reply.
The problem is that I am on CentOS 7 and this is the latest gnupg version that comes with the distribution. I can see there is no easy upgrade (no rpms or repository) readily available and I am afraid that installing in from source might cause some problems with any other parts of CentOS that depends on the other version of gnupg or libgpg-error, libgcrypt, libassuan, .... Lacking any clear upgrade path I am forced to stick with the current version and hope that my scripts will not receive another corrupt file. Thanks again, Lian On 24/06/18 10:52, Werner Koch wrote: > On Thu, 21 Jun 2018 11:40, lian.s...@virusbulletin.com said: > >> 1. Is it "normal" to hang like this or it is a bug ? > No, that should not happen. Compression 42 is clearly an indication for > a corrupt file. > >> 2. Is there any option I can pass to gnupg in command line so that it >> goes on in case of errors instead of hanging? > No, the above looks like a bug which needs to be fixed. > >> /gpg (GnuPG) 2.0.22// > That version is close to 5 years old and its 2.0 branch reached > end-of-life half a year ago. We might have fixed such a bug already in > current versions. > > Please let us know if you can replicate this with a current GnuPG > version and we will dig into it. > > > Shalom-Salam, > > Werner > -- Virus Bulletin Ltd, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, Oxon, United Kingdom. _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
