security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-07-02 22:46:30 +02:00
Code Activity

Fixes for W32

Browse source
This commit is contained in:
Werner Koch 2001-04-19 11:40:45 +00:00
parent 64ddc393e1
commit 397a73b685
36 changed files with 296 additions and 165 deletions
Download patch file Download diff file Expand all files Collapse all files

4
doc/ChangeLog
View file

@ -1,3 +1,7 @@
2001-04-19 Werner Koch <wk@gnupg.org>
* faq.raw: Add a note about dates displayed as ????-??-??.
2001-04-17 Werner Koch <wk@gnupg.org>
* Makefile.am (%.texi): Add rules to create .texi from .sgml.

2
doc/DETAILS
View file

@ -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:

17
doc/FAQ
View file

@ -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

8
doc/faq.raw
View file

@ -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

3
doc/gpg.sgml
View file

@ -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>