mirror of
git://git.gnupg.org/gnupg.git
synced 2025-03-12 23:01:14 +01:00

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>
This is a binary version of GnuPG for MS-Windows 95, 98, WNT, W2000 and XP. A FAQ comes with this package and a probably more recent one can be found online at http://www.gnupg.org/faq.html. See http://www.gnupg.org/docs-mls.html for a list of mailing lists. In particular the list gnupg-users@gnupg.org might be useful to answer questions - but please read the FAQ first. Installation instructions: -------------------------- 1. Unpack the ZIP archive (alright, you already did this). 2. Copy "gpg.exe", "gpgv.exe" and "gpgkeys_ldap.exe" to a place where you usually store your binaries. 3. Create a directory "c:\gnupg" (or any other as you like) 4. If you did not use the default directory "c:\gnupg", you should enter a string with the directory into the Registry under the key: HKEY_CURRENT_USER -> Software -> GNU -> GnuPG (you probably need to create the keys GNU and GnuPG) and insert a new string under the name "HomeDir" with the value of the default directory you want to use. Please use forward slashes and not the backslashes when setting filenames for GnuPG into the Registry. 5. Enter "gpg" and see what happens 6. Read the file README and the online HOWTOs Internationalization support: ----------------------------- 1. Decide where to store the translation files for your language. Here we assume the directory "c:/gnu/locale/fr" 2. Set the directory with the translations into the Registry under the key: HKEY_CURRENT_USER -> Control Panel -> Mingw32 -> NLS (you probably need to create the keys Mingw32 and NLS) using a string entry with the name "MoDir". 3. Select which language to use and copy the currect translation file under the name "gnupg.mo" into the directory set in step 2 (Example: "copy fr.mo c:\gnu\locale\fr\gnupg.mo") 4. Done. Currently we only support the Codepages 437, 850 und Latin1. If you have problems, either delete the gnupg.mo file or don't set the environment variable How to build it from the source: -------------------------------- This version has been build with the Mingw32/CPD kit using the latest stable version of GnuPG. First get the source: It has to be available at the same location you found this binary package - if not you should have received a written offer to get the source delivered to you See the file COPYING (section 3) for details. If you got this package from its canonical place (ftp.gnupg.org), the source is available at: ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.2.n.tar.gz or for development snapshots ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.x.n.tar.gz this is the same source as for the Unix version. If your binary version of GnuPG is called something like gnupg-w32-1.0.4-1.zip, you should find a patch file named gnupg-w32-1.0.4-1.0.4-1.diff.gz at the same location, which has to be applied to the stock gpg source file. Instructions are at the top of this file. To build it, you need the MingW32/CPD kit, which is available at ftp://ftp.gnupg.org/people/werner/cpd/mingw32-cpd-0.3.2.tar.gz ftp://ftp.gnupg.org/people/werner/cpd/gcc-core-2.95.2.tar.gz ftp://ftp.gnupg.org/people/werner/cpd/binutils-2.9.1.tar.gz gcc and binutils are stock GNU source which are available at every GNU mirror. After you have installed this environment you should be able to do this: $ scripts/autogen.sh --build-w32 $ make $ mingw32 strip g10/gpg.exe $ cp g10/gpg.exe /some_windows_drive/ And everything hopefully works. If there is a make problem in the "po" directory you can eiterignore it or do a "touch po/all". To build the distribtion ZIP file, you have to create a directory "dist-w32" and run "scripts/mk-w32-dist" right after a successul make run. Don't forget that MS-Windows ist just a temporary workaround until you can switch to a GNU system ;-) Be the source always with you. Werner