diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/ChangeLog | 4 | ||||
| -rw-r--r-- | doc/DETAILS | 2 | ||||
| -rw-r--r-- | doc/FAQ | 17 | ||||
| -rw-r--r-- | doc/faq.raw | 8 | ||||
| -rw-r--r-- | doc/gpg.sgml | 3 |
5 files changed, 29 insertions, 5 deletions
diff --git a/doc/ChangeLog b/doc/ChangeLog index 558423932..32c19c240 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,7 @@ +2001-04-19 Werner Koch <[email protected]> + + * faq.raw: Add a note about dates displayed as ????-??-??. + 2001-04-17 Werner Koch <[email protected]> * Makefile.am (%.texi): Add rules to create .texi from .sgml. diff --git a/doc/DETAILS b/doc/DETAILS index 4249d24a1..a75ca663f 100644 --- a/doc/DETAILS +++ b/doc/DETAILS @@ -56,6 +56,8 @@ ssb::1536:20:5CE086B5B5A18FF4:1998-07-07:0::: addition to these letters, uppercase version of the letter to denote the _usable_ capabilities of the entire key. +All dates are displayed in the format yyyy-mm-dd unless you use the option +--fixed-list-mode in which case they are dispplay as seconds since epoch. More fields may be added later. If field 1 has the tag "pkd", a listing looks like this: @@ -83,8 +83,9 @@ you could search in the mailing list archive. 6.11) I get "gpg: waiting for lock ..." 6.12) Older gpg's (e.g., 1.0) have problems with keys from newer gpgs ... 6.13) With 1.0.4, I get "this cipher algorithm is deprecated ..." - 6.14) I still have a problem. How do I report a bug? - 6.15) Why doesn't GnuPG support X509 certificates? + 6.14) Some dates are displayed as ????-??-??, why? + 6.15) I still have a problem. How do I report a bug? + 6.16) Why doesn't GnuPG support X509 certificates? 7. ADVANCED TOPICS 7.1) How does this whole thing work? @@ -665,7 +666,15 @@ in it - why? "deprecated". Ignore this warning, more recent versions of gpg are corrected. -6.14) I still have a problem. How do I report a bug? +6.14) Some dates are displayed as ????-??-??, why? + + Due to constraints in most libc implementations, dates beyond + 2038-01-19 can't be displayed correctly. 64 bit OSes are not + affected by this problem. To avoid printing wrong dates, GnuPG + instead prints some question marks. To see the correct value, you + can use the options --with-colons and --fixed-list-mode. + +6.15) I still have a problem. How do I report a bug? Are you sure that it's not been mentioned somewhere on the mailing lists? Did you have a look at the bug list (You'll find a link to @@ -674,7 +683,7 @@ in it - why? list. Otherwise, use the GUUG bug tracking system http://bugs.guug.de/Reporting.html. -6.15) Why doesn't GnuPG support X509 certificates? +6.16) Why doesn't GnuPG support X509 certificates? GnuPG, first and foremost, is an implementation of the OpenPGP standard (RFC 2440), which is a competing infrastructure, different diff --git a/doc/faq.raw b/doc/faq.raw index bc9170dfd..7b1702be6 100644 --- a/doc/faq.raw +++ b/doc/faq.raw @@ -632,6 +632,14 @@ in it - why? "deprecated". Ignore this warning, more recent versions of gpg are corrected. +<Q> Some dates are displayed as ????-??-??, why? + + Due to constraints in most libc implementations, dates beyond + 2038-01-19 can't be displayed correctly. 64 bit OSes are not + affected by this problem. To avoid printing wrong dates, GnuPG + instead prints some question marks. To see the correct value, you + can use the options --with-colons and --fixed-list-mode. + <Q> I still have a problem. How do I report a bug? Are you sure that it's not been mentioned somewhere on the mailing diff --git a/doc/gpg.sgml b/doc/gpg.sgml index 150b35ba4..0ddaca95c 100644 --- a/doc/gpg.sgml +++ b/doc/gpg.sgml @@ -1377,7 +1377,8 @@ in future versions. <varlistentry> <term>--fixed-list-mode</term> <listitem><para> -Do not merge user ID and primary key in --with-colon listing mode. +Do not merge user ID and primary key in --with-colon listing mode and +print all timestamps as seconds since 1970-01-01. </para></listitem></varlistentry> <varlistentry> |