security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2024-09-22 15:11:41 +02:00
Code Activity

* Add pointer in --ignore-time-conflict to see --ignore-valid from, and

Browse Source 
vice versa.
This commit is contained in:
David Shaw 2003-06-18 13:16:20 +00:00
parent 7bf7cdb476
commit f80c14b8ef
2 changed files with 12 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/ChangeLog
View File

@ -1,5 +1,8 @@
2003-06-18 David Shaw <dshaw@jabberwocky.com> 2003-06-18 David Shaw <dshaw@jabberwocky.com>
* Add pointer in --ignore-time-conflict to see --ignore-valid
from, and vice versa.
* Document --set-notation. Explain why it is not possible to * Document --set-notation. Explain why it is not possible to
disable permission warnings in the gpg.conf file about the disable permission warnings in the gpg.conf file about the
homedir. homedir.

16
doc/gpg.sgml
View File

@ -1884,18 +1884,20 @@ it does not ensure the de-facto standard format of user IDs.
<term>--ignore-time-conflict</term> <term>--ignore-time-conflict</term>
<listitem><para> <listitem><para>
GnuPG normally checks that the timestamps associated with keys and GnuPG normally checks that the timestamps associated with keys and
signatures have plausible values. However, sometimes a signature seems to signatures have plausible values. However, sometimes a signature
be older than the key due to clock problems. This option makes these seems to be older than the key due to clock problems. This option
checks just a warning. makes these checks just a warning. See also --ignore-valid-from for
timestamp issues on subkeys.
</para></listitem></varlistentry> </para></listitem></varlistentry>
<varlistentry> <varlistentry>
<term>--ignore-valid-from</term> <term>--ignore-valid-from</term>
<listitem><para> <listitem><para>
GnuPG normally does not select and use subkeys created in the future. This GnuPG normally does not select and use subkeys created in the future.
option allows the use of such keys and thus exhibits the pre-1.0.7 This option allows the use of such keys and thus exhibits the
behaviour. You should not use this option unless you there is some pre-1.0.7 behaviour. You should not use this option unless you there
clock problem. is some clock problem. See also --ignore-time-conflict for timestamp
issues with signatures.
</para></listitem></varlistentry> </para></listitem></varlistentry>
<varlistentry> <varlistentry>