[Pkg-gnupg-commit] [gnupg2] 10/21: gpgv: Initialize compliance checker.

[Daniel Kahn Gillmor]

This is an automated email from the git hooks/post-receive script.

dkg pushed a commit to branch master
in repository gnupg2.

commit 006ca124ed95845d43af8c14d7ab2bc085b47b4c
Author: Werner Koch <wk at gnupg.org>
Date:   Wed Sep 13 09:18:15 2017 +0200

    gpgv: Initialize compliance checker.
    
    * g10/gpgv.c (main): Call gnupg_initialize_compliance.
    --
    
    The compliance checker needs to be initialize so that it won't let
    spit out a "not suitable" message.  We use the module name of gpg.
    Because there is no option to change the compliance mode in gpgv we
    will always be in the default (CO_GNUPG) mode.  It also does not make
    much sense to have it here because gpgv expects a "curated" keyring.
    
    GnuPG-bug-id: 3404
    Signed-off-by: Werner Koch <wk at gnupg.org>
---
 g10/gpgv.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/g10/gpgv.c b/g10/gpgv.c
index fb274b3..c43067d 100644
--- a/g10/gpgv.c
+++ b/g10/gpgv.c
@@ -202,6 +202,7 @@ main( int argc, char **argv )
   dotlock_disable ();
   gcry_control (GCRYCTL_INITIALIZATION_FINISHED, 0);
   additional_weak_digest("MD5");
+  gnupg_initialize_compliance (GNUPG_MODULE_NAME_GPG);
 
   pargs.argc = &argc;
   pargs.argv = &argv;

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-gnupg/gnupg2.git