| Subject: | Shouldn't --trust-model=always imply --no-auto-check-trustdb? |
Hi,
This should probably have been merged with #93707, sorry for the noise.
As of GnuPG 1.4.16/2.0.22, --trust-model=always no longer triggers the creation of a trustdb for operations that modify the public keyring (e.g., --import or --edit). However, when a trustdb is already present, an ugly message leaks to the error output (the logger FD, to be precise) instead
gpg: no need for a trustdb check with `always' trust model
A way around it is to pass --no-auto-check-trustdb to gpg. I wonder if there is any reason not to do it when the GnuPG::Interface object is created with 'always_trust'?
--8<-------------------------------------------------------------->8-- --- a/GnuPG/Options.pm
+++ b/GnuPG/Options.pm
@@ -130,7 +130,7 @@
push @args, '--no-verbose' if $self->no_verbose();
push @args, '--quiet' if $self->quiet();
push @args, '--batch' if $self->batch();
- push @args, '--trust-model=always' if $self->always_trust();
+ push @args, '--trust-model=always', '--no-auto-check-trustdb' if $self->always_trust();
push @args, '--comment', $self->comment() if defined $self->comment();
push @args, '--force-v3-sigs' if $self->force_v3_sigs();
push @args, '--rfc1991' if $self->rfc1991; --8<-------------------------------------------------------------->8--
Cheers,
--
Guilhem.