decrypt-file updates trustdb?

[David.Vazquez-Landa at ecb.int]

Dear Werner,

Yes, I found that option when browsing through the documentation. The reason I haven't started using it is that first I would like to understand why, if I'm just decrypting a file, gpg asks for write permission to trustdb.gpg, pubring.gpg and pubring.bak. In other words, I wouldn't expect my command to have to write anything. Alas, I haven't found enough information on what gpg does when running decrypt-file (or list-keys, for that matter, which gives me the same issue).

Best Regards,

David Vázquez
EDEN Team
European Central Bank
__________________ 
Tel. (+49) 69 1344 7029
Mail. david.vazquez-landa at ecb.europa.eu

> -----Original Message-----
> From: Werner Koch [mailto:wk at gnupg.org]
> Sent: Friday 24 February 2012 14:39
> To: Vazquez Landa, David
> Cc: ciamarie at my180.net; gnupg-users at gnupg.org
> Subject: Re: decrypt-file updates trustdb?
> 
> On Thu, 23 Feb 2012 14:19, David.Vazquez-Landa at ecb.int said:
> 
> > I don't know if this applies in my case. I forgot to add --sorry-- that the
> service is running on a Windows 2008 machine.
> 
> I have not closely looked at your report.  However, you may want to try
> this option:
> 
>   @item --ignore-time-conflict
> 
>   GnuPG normally checks that the timestamps associated with keys and
>   signatures have plausible values. However, sometimes a signature
>   seems to be older than the key due to clock problems. This option
>   makes these checks just a warning. See also @option{--ignore-valid-from}
> for
>   timestamp issues on subkeys.
> 
> 
> Salam-Shalom,
> 
>    Werner
> 
> --
> Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.





Any e-mail message from the European Central Bank (ECB) is sent in good faith but shall neither be binding nor construed as constituting a commitment by the ECB except where provided for in a written agreement. This e-mail is intended only for the use of the recipient(s) named above. Any unauthorised disclosure, use or dissemination, either in whole or in part, is prohibited. If you have received this e-mail in error, please notify the sender immediately via e-mail and delete this e-mail from your system.