to $hGPGHTTP and update instances of variable throughout FAQ in
introduction area and sections 1.1, 2.1 and 2.2
* Added section 1.4 - What conventions are used in this FAQ?
+ unices vs. win32 (with hyperlink (<Rhomedir>) to section 4.18 for
example
+ gpg.conf vs. options (with hyperlink (<Roptions>) to section 5.8
to note name change
* Corrected section 2.2 - Changed ftp URL (both display and link URLs)
from "ftp://ftp.gnupg.org/pub/gcrypt" to ftp://ftp.gnupg.org/gcrypt/,
and the display URL (not the actual link URL, it's correct) of the http
URL from "http://www.gnupg.org/mirror.html" to
"http://www.gnupg.org/mirrors.html"
* Included variable ($hVERSION) for easier updating of latest gpg
version when referenced (as in section 2.2)
* Included variable ($hGPGFTP) for default gnupg.org ftp location
(ftp://ftp.gnupg.org) for use in sections 2.2 and 4.16
* Corrected section 3.1 visual display of link from
"http://www.gnupg.org/gnupg.html#supsys" to
"http://www.gnupg.org/backend.html#supsys"
* Edited sections 3.1, 3.2, 5.2 to include $hGPGHTTP variable
* Corrected section 3.2 - Word typo ("avoided" was "avoiced").
* Corrected / edited section 3.3 -
+ corrected link: ftp://ftp.gnupg.dk/pub/contrib-dk/
for idea.c.gz, idea.c.gz.sig, ideadll.zip, ideadll.zip.sig
+ edited section to include all files and added
~/.gnupg/gpg.conf info
* Edited section 4.6 - As this section deals with loosing a public key,
I added a paragraph containing a hyperlink to the end of section 4.21
("I still have my secret key, but lost my public key..."). The
paragraph reads: "If you've lost your public key and need to recreate
it instead for continued use with your secret key, you may be able to
use gpgsplit as detailed in question <Rgpgsplit>."
* Edited section 4.15 - Added paragraph below table on GPGrelay, an
application for MUAs that lack OpenPGP (rfc2015) support to. "Users of
Win32 MUAs that lack OpenPGP support may look into using GPGrelay
<http://http://gpgrelay.sourceforge.net>, a small email-relaying
server that uses GnuPG to enable many email clients to send and
receive emails that conform to PGP-MIME (RFC 2015)."
suggested by: Andreas John <aj@tesla.inka.de>
* Corrected section 4.16 - Incorportated Werner's URL fix for gpgme FTP
location to synchronize local CVS with released FAQ version 1.5.8.
* Added section 4.19 - "How do I verify signed packages?"
suggested by: Christian Reis <kiko@async.com.br>
* Added section 4.20 - "How do I export a keyring with only selected
signatures?"
by: David Shaw <dshaw@jabberwocky.com>
* Added section 4.21 - "I still have my secret key, but lost my public
key. What can I do?"
by: Werner Koch <wk@gnupg.org>
* Added section 4.22 - "Clearsigned messages sent from my web-mail
account have an invalid signature. Why?"
by: David Scribner <dscribner@bigfoot.com>
* Edited / Corrected section 5.8 - Changed question from "I just
installed the most recent version of GnuPG and don't have a
~/.gnupg/options file. Is this missing from the installation?" to
"GnuPG no longer installs a ~/.gnupg/options file. Is it missing?"
+ Added "An existing options file can be renamed to gpg.conf for
users upgrading, or receiving the message that the "old default
options file" is ignored (occurs if both a gpg.conf and an
options file are found)." to the end of the paragraph.
+ Corrected ~/.gnupg/gpg.conf (was ~/.gnupg/conf)
* Added section 5.9 - "How to you export GnuPG keys for use with PGP?"
by: David Shaw <dshaw@jabberwocky.com>
* options.h (opt): Added mangle-dos-filenames.
* openfile.c (open_outfile) [USE_ONLY_8DOT3]: Truncate the
filename only when this option is set; this is the default.
NOT YET TESTED!
Minimal isn't always best.
* sign.c (update_keysig_packet): Use the current time rather then a
modification of the original signature time. Make sure that this doesn't
cause a time warp.
* keygen.c (keygen_add_key_expire): Properly handle a key expiration date
in the past (use a duration of 0).
* keyedit.c (menu_expire): Use update_keysig_packet so any sig subpackets
are maintained during the update.
* build-packet.c (build_sig_subpkt): Mark sig expired or unexpired when
the sig expiration subpacket is added. (build_sig_subpkt_from_sig): Handle
making an expiration subpacket from a sig that has already expired (use a
duration of 0).
pkclist.c (algo_available), revoke.c (gen_revoke): Add --pgp8 mode. This
is basically identical to --pgp7 in all ways except that signing subkeys,
v4 data sigs (including expiration), and SK comments are allowed.
* getkey.c (finish_lookup): Comment.
user ID display in the --edit-key menu to match that of the --list-keys
display.
* tdbio.c (tdbio_read_record, tdbio_write_record): Comments to reserve a
byte for trust model in the devel version.
* g10.c (add_notation_data): Fix initialization.
expiration date of a subkey. This is not the most optimal solution, but
it is minimal change on the stable branch.
* main.h, keygen.c (do_copy_key_flags): New function to copy key flags, if
any, from one sig to another. (do_add_key_expire): New function to add key
expiration to a sig. (keygen_copy_flags_add_expire): New version of
keygen_add_key_expire that also copies key flags.
(keygen_add_key_flags_and_expire): Use do_add_key_expire.
* import.c (fix_hkp_corruption): Comment.
--cert-notation. Clarify --show-notation and --show-policy-url that
policy URLs and notations can be used in data signatures as well. Add
note about '@' being a required character in notation names.
'@', unless --expert is set. This is to help prevent people from
polluting the (as yet unused) IETF namespace.
* main.h: Comments about default algorithms.
* photoid.c (image_type_to_string): Comments about 3-letter file
extensions.
* g10.c (main): Add --strict and --no-strict as no-ops to smooth
transition when the devel GnuPG becomes the stable one.
display match the validity and trust of --with-colons --list-keys.
* passphrase.c (agent_send_all_options): Fix compile warning.
* keylist.c (list_keyblock_colon): Validity for subkeys should match that
of the primary key, and not that of the last user ID.
these facts onto all their subkeys, but only after the subkey has a chance
to be marked valid. This is to fix an incorrect "invalid public key"
error verifying a signature made by a revoked signing subkey, with a valid
unrevoked primary key.
(get_pubkey_fast): this and made extern.
(get_pubkey_byfprint_fast): New.
* import.c (import_one): Use get_pubkey_fast instead of
get_pubkey. We don't need a merged key and actually this might
lead to recursions. --> There is still a problem, though.
(revocation_present): Likewise for search by fingerprint.
* g10.c (main): Try to create the trustdb even for non-colon-mode
list-key operations. This is required because getkey needs to
know whether a a key is ultimately trusted.
