Future Time, --ignore-time-conflict doesn't work!

David Shaw dshaw at jabberwocky.com
Fri May 30 16:43:02 CEST 2003

Hash: SHA1

On Fri, May 30, 2003 at 05:36:37PM +0930, jonathan soong wrote:
> Hi everyone,
> I am currently experiencing a problem with future-created keys and was 
> wondering if there was a work around.
> Any help would be most appreciated.
> -----------------------------------------------------------------------
> The Problem:
> -----------------------------------------------------------------------
> e.g.
> Step 1. Comp A has a future time (110 seconds in this example) - it 
> generates a key and sends it to the Keyserver.
> Step 2. Comp B imports Comp A's key from the keyserver:

> Step 3. Comp B then tries to use Comp A's key to encode something
>    $> /usr/bin/gpg  --ignore-time-conflict  --homedir gpg -e  -r  	
>       ABA2D44E
>    $> gpg: ABA2D44E: skipped: unusable public key
>    $> gpg: [stdin]: encryption failed: unusable public key
> -------------------------------------------------------------------------
> Is this correct behaviour? Shouldn't the '--ignore-time-conflict' flag 
> in step three allow it to encode anyway?
> In the above example, the key was 110 seconds in the future (see step 
> 2), after 110 seconds, step three is successful.
> What is the point of the "--ignore-time-conflict" in this situation? It 
> doesn't seem to do anything.. :(

Hmm.  I can't duplicate the problem, so I need more information.  What
version of GnuPG is this?  What kind of key is 0xABA2D44E?  What
happens if you do the same thing with --ignore-valid-from set?

Version: GnuPG v1.2.3-cvs (GNU/Linux)
Comment: http://www.jabberwocky.com/david/keys.asc


More information about the Gnupg-devel mailing list