[Pkg-gnupg-commit] r97 - in /gnupg-doc/trunk: debian/ gph/ gph/es/ gph/ru/ mini_howto/ mini_howto/de/ mini_howto/en/ mini_howto/es/ mini_howto/nl/ pgp2x/ pgp2x/en/ pgp2x/es/
dleidert-guest at users.alioth.debian.org
dleidert-guest at users.alioth.debian.org
Fri May 8 09:00:28 UTC 2009
Author: dleidert-guest
Date: Fri May 8 09:00:27 2009
New Revision: 97
URL: http://svn.debian.org/wsvn/pkg-gnupg/?sc=1&rev=97
Log:
[svn-inject] Applying Debian modifications to trunk
Added:
gnupg-doc/trunk/debian/ (with props)
gnupg-doc/trunk/debian/changelog
gnupg-doc/trunk/debian/control
gnupg-doc/trunk/debian/copyright
gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook
gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-de
gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-es
gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-fr
gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-it
gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-ru
gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto
gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-ca
gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-ch
gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-de
gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-es
gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-fr
gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-nl
gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-pt
gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-se
gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-vn
gnupg-doc/trunk/debian/doc-base-gnupg-to-pgp2x
gnupg-doc/trunk/debian/doc-base-gnupg-to-pgp2x-es
gnupg-doc/trunk/debian/postinst
gnupg-doc/trunk/debian/prerm
gnupg-doc/trunk/debian/rules (with props)
gnupg-doc/trunk/gph/
gnupg-doc/trunk/gph/Makefile.am
gnupg-doc/trunk/gph/configure.in
gnupg-doc/trunk/gph/db2any (with props)
gnupg-doc/trunk/gph/es/
gnupg-doc/trunk/gph/es/c3.sgml
gnupg-doc/trunk/gph/ru/
gnupg-doc/trunk/gph/ru/Makefile.am
gnupg-doc/trunk/mini_howto/
gnupg-doc/trunk/mini_howto/de/
gnupg-doc/trunk/mini_howto/de/Makefile
gnupg-doc/trunk/mini_howto/en/
gnupg-doc/trunk/mini_howto/en/GPGMiniHowto.sgml
gnupg-doc/trunk/mini_howto/en/Makefile
gnupg-doc/trunk/mini_howto/es/
gnupg-doc/trunk/mini_howto/es/Makefile
gnupg-doc/trunk/mini_howto/nl/
gnupg-doc/trunk/mini_howto/nl/Makefile
gnupg-doc/trunk/pgp2x/
gnupg-doc/trunk/pgp2x/en/
gnupg-doc/trunk/pgp2x/en/Makefile
gnupg-doc/trunk/pgp2x/es/
gnupg-doc/trunk/pgp2x/es/Makefile
Propchange: gnupg-doc/trunk/debian/
------------------------------------------------------------------------------
mergeWithUpstream = 1
Added: gnupg-doc/trunk/debian/changelog
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/changelog?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/changelog (added)
+++ gnupg-doc/trunk/debian/changelog Fri May 8 09:00:27 2009
@@ -1,0 +1,140 @@
+gnupg-doc (2003.04.06+dak1-0.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Reupload to include the source tarball, missing since the move to
+ main, due to a well-known dak bug (Closes: #507445).
+
+ -- Cyril Brulebois <kibi at debian.org> Sun, 07 Dec 2008 09:02:32 +0100
+
+gnupg-doc (2003.04.06-6) unstable; urgency=low
+
+ * debian/control (Section): move back to main, per GR. Closes: #406648
+
+ * debian/postinst, debian/prerm: pass full path to install-docs (because
+ you know, stable APIs are for losers?). Thanks to Florian Kulzer
+ <florian.kulzer at icfo.es>. Closes: #425351
+
+ * doc-base-gnu-privacy-handbook, doc-base-gnu-privacy-handbook-de,
+ doc-base-gnu-privacy-handbook-es, doc-base-gnu-privacy-handbook-fr,
+ doc-base-gnu-privacy-handbook-it, doc-base-gnu-privacy-handbook-ru:
+ fix Index and Files entries to match reality. Closes: #362667, #396757
+
+ * debian/control (Standards-Version): bump to 3.7.2.2.
+ * debian/copyright: update address of FSF. Drop full copy of GFDL,
+ refer to copy in base-files instead.
+
+ -- James Troup <james at nocrew.org> Thu, 20 Sep 2007 02:28:17 +0100
+
+gnupg-doc (2003.04.06-5) unstable; urgency=low
+
+ * debian/control (Section): move to non-free. Closes: #331541
+ * debian/control (Standards-Version): bump to 3.6.2.1.
+ * debian/copyright: Fix cut'n'waste of GPL where LGPL was meant.
+ Closes: #331545
+
+ -- James Troup <james at nocrew.org> Sun, 20 Nov 2005 04:20:55 +0000
+
+gnupg-doc (2003.04.06-4) unstable; urgency=low
+
+ * gph/db2any: search for 'TeX' anywhere in the output of 'jadetex -v',
+ not just the beginning of the line as jadetex recently started talking
+ about the version 'e-TeX' rather than 'TeX'. Thanks to Kurt Roeckx
+ <kurt at roeckx.be> for the report. Closes: #310763
+
+ * debian/rules (binary-indep): install '*.htm' as well as '*.html' when
+ installing files for the GNU Privacy Handbook as jadetex defaults to
+ that now. Create 'index.html' -> 'book1.htm' convenience symlinks to
+ compensate.
+
+ -- James Troup <james at nocrew.org> Wed, 1 Jun 2005 14:58:15 +0100
+
+gnupg-doc (2003.04.06-3) unstable; urgency=low
+
+ * gph/db2any: add '/usr/share/sgml/docbook/stylesheet/dsssl/modular' as
+ one of the possible stylesheet locations.
+ * debian/control (Build-Depends-Indep): add jade. [Both changes are a]
+ patch from Roland Stigge <stigge at antcom.de>. Closes: #278961
+
+ * debian/rules (clean): also remove gph/config.{sub,guess}.
+
+ -- James Troup <james at nocrew.org> Mon, 1 Nov 2004 00:41:06 +0000
+
+gnupg-doc (2003.04.06-2) unstable; urgency=low
+
+ * debian/doc-base-gnu-privacy-handbook-it: Correct path to
+ index-file. (s/book1/index/)
+ * debian/doc-base-gnupg-mini-howto-ch: correct HTML's index path
+ (s/GPGMiniHowto/index/). Correct HTML's files glob by just using
+ '*.html'.
+ * debian/doc-base-gnupg-mini-howto-es: fix filename for text's files and
+ HTML's index (s/GPGMiniHowto/gpgminicomo/). Correct HTML's files glob
+ by just using '*.html'.
+ * debian/doc-base-gnupg-mini-howto-pt: fix filename for HTML's index
+ (s/GPGMiniHowto/gnupg/). Correct HTML's files glob by just using
+ '*.html'.
+ * debian/doc-base-gnupg-mini-howto-vn: fix filename for HTML's index
+ (s/GPGMiniHowto.html/index.htm/). Correct HTML's files glob by just
+ using '*.htm*'.
+ * Thanks to Laurent Bonnaud <Laurent.Bonnaud at inpg.fr> and Axel Krauth
+ <krauth at fmi.uni-passau.de> for noticing the above. Closes: #189746,
+ #190634, #190635
+
+ * debian/control: There is no Swiss mini-HOWTO. Noticed by Meinolf
+ Sander <mesa at netcologne.de>.
+
+ * debian/rules (build): call autoreconf with --install instead of -i
+ since the latter is not recognised by the autoreconf wrapper provided
+ by autoconf2.13.
+
+ -- James Troup <james at nocrew.org> Wed, 4 Jun 2003 20:49:51 +0100
+
+gnupg-doc (2003.04.06-1) unstable; urgency=low
+
+ * New release synced with current GnuPG web pages. Adds:
+ o French, German and Italian translations of the Gnu Privacy Handbook.
+ o Catalan, Chinese, Dutch, Swiss and Vietnamese translations of the
+ mini-HOWTO.
+ * debian/rules: virtually rewriten to support new upstream sources
+ * debian/control (Build-Depends): updated for new upstream version and
+ verified against a clean chroot. Closes: #141156
+
+ * debian/rules: update copyright & version and use install_foo
+ convenience variables.
+ * debian/copyright: update copyright.
+ * debian/changelog: remove local-variables stuff.
+
+ * debian/control (Standards-Version): bump to 3.5.9.0.
+ * debian/postinst, debian/prerm: remove; no longer do /usr/doc symlinks.
+
+ * debian/control (Description): fix two typos (provied and Portugese)
+ noticed by Matt Zimmerman <mdz at debian.org>. Fix capitalization of
+ Privacy Guard and PostScript and "mini-" vs. "Mini ", thanks to
+ Meinolf Sander <mesa at netcologne.de>. Closes: #124689, #146712
+
+ * debian/rules (binary-indep): install signatures.jpg too. Noticed by
+ Igor Belyi <ibelyi at yahoo.com>, Mark Howard <mh at tildemh.com> and
+ Francesco Potorti` <pot at gnu.org>. Closes: #108407, #158623, #182438.
+ * debian/rules (binary-indep): rewritten install code includes missing
+ German GPGMiniHowto-4.html noticed by Mukunda Peter Pasedach
+ <mukunda at mukunda.de>. Closes: #103587
+ * mini_howto/en/GPGMiniHowto.sgml: correct "sing" (sign), "reexported"
+ and "whatsoever". Thanks to Edward Betts <edward at debian.org> for the
+ first one. Closes: #151822
+ * gph/es/c3.sgml: copy SGML from other languages so that TeX-based
+ rendering uses signatures.eps rather than signatures.jpg and avoids
+ bombing out ghostscript and other postscript parsers. Closes: #75378
+
+ * debian/doc-base-*: added doc-base control files for all documents.
+ Thanks to Mikael Hedin <micce at debian.org> for the suggestion.
+ Closes: #158495
+ * debian/rules (binary-indep): install doc-base control files.
+ * debian/postinst: register with doc-base.
+ * debian/prerm: de-register.
+
+ -- James Troup <james at nocrew.org> Wed, 9 Apr 2003 01:49:50 +0100
+
+gnupg-doc (2000.10.01-1) unstable; urgency=low
+
+ * Initial release. [#67564, #65560]
+
+ -- James Troup <james at nocrew.org> Sun, 1 Oct 2000 07:16:07 +0100
Added: gnupg-doc/trunk/debian/control
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/control?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/control (added)
+++ gnupg-doc/trunk/debian/control Fri May 8 09:00:27 2009
@@ -1,0 +1,24 @@
+Source: gnupg-doc
+Section: doc
+Priority: optional
+Maintainer: James Troup <james at nocrew.org>
+Standards-Version: 3.7.2.2
+Build-Depends-Indep: sgmltools-lite, docbook-to-man, docbook-utils, autoconf, automake, linuxdoc-tools-latex, linuxdoc-tools-text, imagemagick, w3m, jade
+
+Package: gnupg-doc
+Architecture: all
+Suggests: gnupg
+Description: GNU Privacy Guard documentation
+ Additional documentation for GnuPG in HTML and (where possible)
+ PostScript and plain text format. Includes:
+ .
+ o The GNU Privacy Handbook
+ o Replacing PGP 2.x with GnuPG
+ o GnuPG mini-HOWTO
+ .
+ The GNU Privacy Handbook is provided in English, French, German,
+ Italian, Spanish and Russian.
+ The Replacing PGP 2.x with GnuPG document is provided in English and
+ Spanish.
+ The mini-HOWTO is provided in English, Catalan, Chinese, Dutch,
+ French, German, Portuguese, Spanish, Swedish and Vietnamese.
Added: gnupg-doc/trunk/debian/copyright
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/copyright?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/copyright (added)
+++ gnupg-doc/trunk/debian/copyright Fri May 8 09:00:27 2009
@@ -1,0 +1,50 @@
+This is Debian GNU's prepackaged version of additional GnuPG
+documentation.
+
+This package was put together by me, James Troup <james at nocrew.org>,
+from the sources, which I obtained from
+ http://www.gnupg.org/docs.html
+
+The GNU Privacy Handbook:
+
+ Copyright (C) 2000 Free Software Foundation, Inc.
+
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the GNU Free Documentation License, Version 1.1
+ or any later version published by the Free Software Foundation;
+ with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
+ A copy of the license is included in the section entitled "GNU
+ Free Documentation License" (and in /usr/share/common-licenses/GFDL).
+
+The GnuPG Mini HOWTO:
+
+ Copyright © 1999 Brenno J.S.A.A.F. de Winter (english version)
+ Copyright © 1999 Michael Fischer v. Mollard (original German version)
+ Copyright © 2002 Arjen Baart (Dutch version)
+
+ This document is free documentation you can redistribute it and/or
+ modify it under the terms of the GNU Library General Public License
+ as published by the Free Software Foundation; either version 2 of
+ the License, or (at your option) any later version.
+
+ This library is distributed in the hope that it will be useful, but
+ WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Library General Public License for more details.
+
+ You should have received a copy of the GNU Library General Public License
+ with your Debian GNU system, in /usr/share/common-licenses/LGPL-2, or
+ with the Debian GNU gnupg source package as the file COPYING. If
+ not, write to the Free Software Foundation, Inc., 51 Franklin St,
+ Fifth Floor, Boston, MA 02110-1301, USA.
+
+Replacing PGP 2.x with GnuPG:
+
+ Copyright © 1999 by Kyle Hasselbacher
+
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the GNU Free Documentation License, Version 1.1
+ or any later version published by the Free Software Foundation;
+ with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
+ A copy of the license is included in the section entitled "GNU
+ Free Documentation License" (and in /usr/share/common-licenses/GFDL).
Added: gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook (added)
+++ gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook Fri May 8 09:00:27 2009
@@ -1,0 +1,12 @@
+Document: gnu-privacy-handbook
+Title: The GNU Privacy Handbook
+Author: Mike Ashley
+Abstract: This is an depth guide for GNU Privacy Guard (GnuPG).
+Section: Apps/Tools
+
+Format: text
+Files: /usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/manual.txt.gz
+
+Format: HTML
+Index: /usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/html/book1.htm
+Files: /usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/html/*.htm
Added: gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-de
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-de?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-de (added)
+++ gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-de Fri May 8 09:00:27 2009
@@ -1,0 +1,12 @@
+Document: gnu-privacy-handbook-de
+Title: The GNU Privacy Handbook (German)
+Author: Mike Ashley
+Abstract: This is an depth guide for GNU Privacy Guard (GnuPG) in German.
+Section: Apps/Tools
+
+Format: text
+Files: /usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/de/manual.txt.gz
+
+Format: HTML
+Index: /usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/de/html/book1.htm
+Files: /usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/de/html/*.htm
Added: gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-es
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-es?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-es (added)
+++ gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-es Fri May 8 09:00:27 2009
@@ -1,0 +1,12 @@
+Document: gnu-privacy-handbook-es
+Title: The GNU Privacy Handbook (Spanish)
+Author: Mike Ashley
+Abstract: This is an depth guide for GNU Privacy Guard (GnuPG) in Spanish.
+Section: Apps/Tools
+
+Format: text
+Files: /usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/es/manual.txt.gz
+
+Format: HTML
+Index: /usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/es/html/book1.htm
+Files: /usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/es/html/*.htm
Added: gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-fr
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-fr?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-fr (added)
+++ gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-fr Fri May 8 09:00:27 2009
@@ -1,0 +1,12 @@
+Document: gnu-privacy-handbook-fr
+Title: The GNU Privacy Handbook (French)
+Author: Mike Ashley
+Abstract: This is an depth guide for GNU Privacy Guard (GnuPG) in French.
+Section: Apps/Tools
+
+Format: text
+Files: /usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/fr/manual.txt.gz
+
+Format: HTML
+Index: /usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/fr/html/book1.htm
+Files: /usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/fr/html/*.htm
Added: gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-it
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-it?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-it (added)
+++ gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-it Fri May 8 09:00:27 2009
@@ -1,0 +1,12 @@
+Document: gnu-privacy-handbook-it
+Title: The GNU Privacy Handbook (Italian)
+Author: Mike Ashley
+Abstract: This is an depth guide for GNU Privacy Guard (GnuPG) in Italian.
+Section: Apps/Tools
+
+Format: text
+Files: /usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/it/manual.txt.gz
+
+Format: HTML
+Index: /usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/it/html/book1.htm
+Files: /usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/it/html/*.htm
Added: gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-ru
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-ru?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-ru (added)
+++ gnupg-doc/trunk/debian/doc-base-gnu-privacy-handbook-ru Fri May 8 09:00:27 2009
@@ -1,0 +1,12 @@
+Document: gnu-privacy-handbook-ru
+Title: The GNU Privacy Handbook (Russian)
+Author: Mike Ashley
+Abstract: This is an depth guide for GNU Privacy Guard (GnuPG) in Russian.
+Section: Apps/Tools
+
+Format: text
+Files: /usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/ru/manual.txt.gz
+
+Format: HTML
+Index: /usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/ru/html/book1.htm
+Files: /usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/ru/html/*.htm
Added: gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto (added)
+++ gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto Fri May 8 09:00:27 2009
@@ -1,0 +1,12 @@
+Document: gnupg-mini-howto
+Title: Gnu Privacy Guard (GnuPG) mini-HOWTO
+Author: Brenno J.S.A.A.F. de Winter, Michael Fischer v. Mollard
+Abstract: This is a mini-HOWTO for Gnu Privacy Guard (GnuPG).
+Section: Apps/Tools
+
+Format: text
+Files: /usr/share/doc/gnupg-doc/mini-HOWTO/GPGMiniHowto.txt.gz
+
+Format: HTML
+Index: /usr/share/doc/gnupg-doc/mini-HOWTO/GPGMiniHowto.html
+Files: /usr/share/doc/gnupg-doc/mini-HOWTO/GPGMiniHowto*.html
Added: gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-ca
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-ca?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-ca (added)
+++ gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-ca Fri May 8 09:00:27 2009
@@ -1,0 +1,12 @@
+Document: gnupg-mini-howto-ca
+Title: Gnu Privacy Guard (GnuPG) mini-HOWTO (Catalan)
+Author: Brenno J.S.A.A.F. de Winter, Michael Fischer v. Mollard
+Abstract: This is a mini-HOWTO for Gnu Privacy Guard (GnuPG) in Catalan.
+Section: Apps/Tools
+
+Format: text
+Files: /usr/share/doc/gnupg-doc/mini-HOWTO/ca/GPGMiniHowto.txt.gz
+
+Format: HTML
+Index: /usr/share/doc/gnupg-doc/mini-HOWTO/ca/GPGMiniHowto.html
+Files: /usr/share/doc/gnupg-doc/mini-HOWTO/ca/GPGMiniHowto*.html
Added: gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-ch
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-ch?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-ch (added)
+++ gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-ch Fri May 8 09:00:27 2009
@@ -1,0 +1,9 @@
+Document: gnupg-mini-howto-ch
+Title: Gnu Privacy Guard (GnuPG) mini-HOWTO (Chinese)
+Author: Brenno J.S.A.A.F. de Winter, Michael Fischer v. Mollard
+Abstract: This is a mini-HOWTO for Gnu Privacy Guard (GnuPG) in Chinese.
+Section: Apps/Tools
+
+Format: HTML
+Index: /usr/share/doc/gnupg-doc/mini-HOWTO/ch/index.html
+Files: /usr/share/doc/gnupg-doc/mini-HOWTO/ch/*.html
Added: gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-de
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-de?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-de (added)
+++ gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-de Fri May 8 09:00:27 2009
@@ -1,0 +1,12 @@
+Document: gnupg-mini-howto-de
+Title: Gnu Privacy Guard (GnuPG) mini-HOWTO (German)
+Author: Brenno J.S.A.A.F. de Winter, Michael Fischer v. Mollard
+Abstract: This is a mini-HOWTO for Gnu Privacy Guard (GnuPG) in German.
+Section: Apps/Tools
+
+Format: text
+Files: /usr/share/doc/gnupg-doc/mini-HOWTO/de/GPGMiniHowto.txt.gz
+
+Format: HTML
+Index: /usr/share/doc/gnupg-doc/mini-HOWTO/de/GPGMiniHowto.html
+Files: /usr/share/doc/gnupg-doc/mini-HOWTO/de/GPGMiniHowto*.html
Added: gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-es
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-es?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-es (added)
+++ gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-es Fri May 8 09:00:27 2009
@@ -1,0 +1,12 @@
+Document: gnupg-mini-howto-es
+Title: Gnu Privacy Guard (GnuPG) mini-HOWTO (Spanish)
+Author: Brenno J.S.A.A.F. de Winter, Michael Fischer v. Mollard
+Abstract: This is a mini-HOWTO for Gnu Privacy Guard (GnuPG) in Spanish.
+Section: Apps/Tools
+
+Format: text
+Files: /usr/share/doc/gnupg-doc/mini-HOWTO/es/gpgminicomo.txt.gz
+
+Format: HTML
+Index: /usr/share/doc/gnupg-doc/mini-HOWTO/es/gpgminicomo.html
+Files: /usr/share/doc/gnupg-doc/mini-HOWTO/es/*.html
Added: gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-fr
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-fr?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-fr (added)
+++ gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-fr Fri May 8 09:00:27 2009
@@ -1,0 +1,9 @@
+Document: gnupg-mini-howto-fr
+Title: Gnu Privacy Guard (GnuPG) mini-HOWTO (French)
+Author: Brenno J.S.A.A.F. de Winter, Michael Fischer v. Mollard
+Abstract: This is a mini-HOWTO for Gnu Privacy Guard (GnuPG) in French.
+Section: Apps/Tools
+
+Format: HTML
+Index: /usr/share/doc/gnupg-doc/mini-HOWTO/fr/GPGMiniHowto.html
+Files: /usr/share/doc/gnupg-doc/mini-HOWTO/fr/GPGMiniHowto*.html
Added: gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-nl
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-nl?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-nl (added)
+++ gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-nl Fri May 8 09:00:27 2009
@@ -1,0 +1,12 @@
+Document: gnupg-mini-howto-nl
+Title: Gnu Privacy Guard (GnuPG) mini-HOWTO (Dutch)
+Author: Brenno J.S.A.A.F. de Winter, Michael Fischer v. Mollard
+Abstract: This is a mini-HOWTO for Gnu Privacy Guard (GnuPG) in Dutch.
+Section: Apps/Tools
+
+Format: text
+Files: /usr/share/doc/gnupg-doc/mini-HOWTO/nl/GPGMiniHowto.txt.gz
+
+Format: HTML
+Index: /usr/share/doc/gnupg-doc/mini-HOWTO/nl/GPGMiniHowto.html
+Files: /usr/share/doc/gnupg-doc/mini-HOWTO/nl/GPGMiniHowto*.html
Added: gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-pt
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-pt?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-pt (added)
+++ gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-pt Fri May 8 09:00:27 2009
@@ -1,0 +1,9 @@
+Document: gnupg-mini-howto-pt
+Title: Gnu Privacy Guard (GnuPG) mini-HOWTO (Portuguese)
+Author: Brenno J.S.A.A.F. de Winter, Michael Fischer v. Mollard
+Abstract: This is a mini-HOWTO for Gnu Privacy Guard (GnuPG) in Portuguese.
+Section: Apps/Tools
+
+Format: HTML
+Index: /usr/share/doc/gnupg-doc/mini-HOWTO/pt/gnupg.html
+Files: /usr/share/doc/gnupg-doc/mini-HOWTO/pt/*.html
Added: gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-se
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-se?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-se (added)
+++ gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-se Fri May 8 09:00:27 2009
@@ -1,0 +1,9 @@
+Document: gnupg-mini-howto-se
+Title: Gnu Privacy Guard (GnuPG) mini-HOWTO (Swedish)
+Author: Brenno J.S.A.A.F. de Winter, Michael Fischer v. Mollard
+Abstract: This is a mini-HOWTO for Gnu Privacy Guard (GnuPG) in Swedish.
+Section: Apps/Tools
+
+Format: HTML
+Index: /usr/share/doc/gnupg-doc/mini-HOWTO/se/GPGMiniHowto.html
+Files: /usr/share/doc/gnupg-doc/mini-HOWTO/se/GPGMiniHowto*.html
Added: gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-vn
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-vn?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-vn (added)
+++ gnupg-doc/trunk/debian/doc-base-gnupg-mini-howto-vn Fri May 8 09:00:27 2009
@@ -1,0 +1,9 @@
+Document: gnupg-mini-howto-vn
+Title: Gnu Privacy Guard (GnuPG) mini-HOWTO (Vietnamese)
+Author: Brenno J.S.A.A.F. de Winter, Michael Fischer v. Mollard
+Abstract: This is a mini-HOWTO for Gnu Privacy Guard (GnuPG) in Vietnamese.
+Section: Apps/Tools
+
+Format: HTML
+Index: /usr/share/doc/gnupg-doc/mini-HOWTO/vn/index.htm
+Files: /usr/share/doc/gnupg-doc/mini-HOWTO/vn/*.htm*
Added: gnupg-doc/trunk/debian/doc-base-gnupg-to-pgp2x
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/doc-base-gnupg-to-pgp2x?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/doc-base-gnupg-to-pgp2x (added)
+++ gnupg-doc/trunk/debian/doc-base-gnupg-to-pgp2x Fri May 8 09:00:27 2009
@@ -1,0 +1,12 @@
+Document: gnupg-to-pgp2x
+Title: Gnu Privacy Guard (GnuPG) mini-HOWTO
+Author: Mike Ashley, Kyle Hasselbacher, Michael Fischer v. Mollard
+Abstract: This is an article on replacing PGP 2.x with GnuPG.
+Section: Apps/Tools
+
+Format: text
+Files: /usr/share/doc/gnupg-doc/pgp2x/pgp2x.txt.gz
+
+Format: HTML
+Index: /usr/share/doc/gnupg-doc/pgp2x/pgp2x.html
+Files: /usr/share/doc/gnupg-doc/pgp2x/pgp2x.html
Added: gnupg-doc/trunk/debian/doc-base-gnupg-to-pgp2x-es
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/doc-base-gnupg-to-pgp2x-es?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/doc-base-gnupg-to-pgp2x-es (added)
+++ gnupg-doc/trunk/debian/doc-base-gnupg-to-pgp2x-es Fri May 8 09:00:27 2009
@@ -1,0 +1,12 @@
+Document: gnupg-to-pgp2x-es
+Title: Gnu Privacy Guard (GnuPG) mini-HOWTO (Spanish)
+Author: Mike Ashley, Kyle Hasselbacher, Michael Fischer v. Mollard
+Abstract: This is an article on replacing PGP 2.x with GnuPG in Spanish.
+Section: Apps/Tools
+
+Format: text
+Files: /usr/share/doc/gnupg-doc/pgp2x/es/pgp2x.txt.gz
+
+Format: HTML
+Index: /usr/share/doc/gnupg-doc/pgp2x/es/pgp2x.html
+Files: /usr/share/doc/gnupg-doc/pgp2x/es/pgp2x.html
Added: gnupg-doc/trunk/debian/postinst
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/postinst?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/postinst (added)
+++ gnupg-doc/trunk/debian/postinst Fri May 8 09:00:27 2009
@@ -1,0 +1,21 @@
+#!/bin/sh
+
+set -e
+
+if [ "$1" = configure ]; then
+ if [ -x /usr/sbin/install-docs ]; then
+ # GPH
+ install-docs -i /usr/share/doc-base/gnu-privacy-handbook
+ for lang in de es fr it ru; do
+ install-docs -i /usr/share/doc-base/gnu-privacy-handbook-$lang
+ done
+ # mini-HOWTO
+ install-docs -i /usr/share/doc-base/gnupg-mini-howto
+ for lang in ca ch de es fr nl pt se vn; do
+ install-docs -i /usr/share/doc-base/gnupg-mini-howto-$lang
+ done
+ # pgp2x
+ install-docs -i /usr/share/doc-base/gnupg-to-pgp2x
+ install-docs -i /usr/share/doc-base/gnupg-to-pgp2x-es
+ fi
+fi
Added: gnupg-doc/trunk/debian/prerm
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/prerm?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/prerm (added)
+++ gnupg-doc/trunk/debian/prerm Fri May 8 09:00:27 2009
@@ -1,0 +1,21 @@
+#!/bin/sh
+
+set -e
+
+if [ "$1" = remove -o "$1" = upgrade ]; then
+ if [ -x /usr/sbin/install-docs ]; then
+ # GPH
+ install-docs -r /usr/share/doc-base/gnu-privacy-handbook
+ for lang in de es fr it ru; do
+ install-docs -r /usr/share/doc-base/gnu-privacy-handbook-$lang
+ done
+ # mini-HOWTO
+ install-docs -r /usr/share/doc-base/gnupg-mini-howto
+ for lang in ca ch de es fr nl pt se vn; do
+ install-docs -r /usr/share/doc-base/gnupg-mini-howto-$lang
+ done
+ # pgp2x
+ install-docs -r /usr/share/doc-base/gnupg-to-pgp2x
+ install-docs -r /usr/share/doc-base/gnupg-to-pgp2x-es
+ fi
+fi
Added: gnupg-doc/trunk/debian/rules
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/debian/rules?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/debian/rules (added)
+++ gnupg-doc/trunk/debian/rules Fri May 8 09:00:27 2009
@@ -1,0 +1,147 @@
+#!/usr/bin/make -f
+# debian/rules file - for gnupg-doc
+# Based on sample debian/rules file - for GNU Hello (1.3).
+# Copyright 1994,1995 by Ian Jackson.
+# Copyright 2000-2004 James Troup
+# I hereby give you perpetual unlimited permission to copy,
+# modify and relicense this file, provided that you do not remove
+# my name from the file itself. (I assert my moral right of
+# paternity under the Copyright, Designs and Patents Act 1988.)
+# This file may have to be extensively modified
+
+install_dir=install -d -m 755
+install_file=install -m 644
+install_script=install -m 755
+install_binary=install -m 755 -s
+
+build:
+ $(checkdir)
+ ## gph
+ cp -vf gph/en/signatures.jpg gph/de/
+ (cd gph; autoreconf -s --install; ./configure)
+ make -C gph > build.log 2>&1
+ # Create text versions
+ for lang in de en es fr it ru; do \
+ (cd gph/$$lang; sgmltools -b w3m manual.sgml >> ../../build.log 2>&1); \
+ done
+ ## pgp2x
+ for j in pgp2x/*; do make -C $$j debian-all; done
+ ## mini-howto
+ for format in html txt ps; do \
+ for lang in $$(find mini_howto -name \*.sgml); do \
+ make -C $$(dirname $$lang) $$(echo $$(basename $$lang) | \
+ sed -e "s/\.sgml/.$$format/") >> build.log 2>&1; \
+ done; \
+ done
+ touch build
+
+clean: checkroot
+ $(checkdir)
+ ## gph
+ -make -C gph distclean > build.log 2>&1;
+ rm -fr gph/autom4te.cache
+ rm -f gph/COPYING gph/install-sh gph/missing gph/mkinstalldirs \
+ gph/configure gph/config.log gph/config.status gph/config.h.in \
+ gph/config.guess gph/config.sub gph/aclocal.m4 \
+ gph/de/signatures.jpg build.log build
+ find gph -name html -type d | xargs rm -fr
+ find gph -name \*.html -o -name \*.ps -o -name \*.refs -o -name \*.texi \
+ -o -name \*.aux -o -name \*.dvi -o -name \*.log -o -name \*.tex \
+ -o -name \*.eps -o -name \*.tmp -o -name \*.txt -o -name Makefile.in \
+ | xargs rm -f
+ ## pgp2x
+ for lang in pgp2x/*; do make -C $$lang clean; done
+ ## mini-howto
+ for i in $$(find mini_howto -name \*.sgml ); do \
+ find $$(dirname $$i) -name \*.txt -o -name \*.html -o -name \*.ps | xargs rm -f; \
+ done
+ -rm -rf debian/tmp debian/files* debian/substvars
+ find . -name \*~ | xargs rm -vf
+
+binary-arch:
+
+binary-indep: build checkroot
+ $(checkdir)
+ -rm -rf debian/tmp
+ $(install_dir) debian/tmp/DEBIAN/
+ $(install_script) debian/prerm debian/postinst debian/tmp/DEBIAN/
+
+ $(install_dir) debian/tmp/usr/share/doc/gnupg-doc/
+
+ ## gph
+ $(install_dir) debian/tmp/usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/
+ for i in gph/de gph/en gph/es gph/fr gph/it gph/ru; do \
+ country=$$(basename $$i); \
+ if [ "$$country" = "en" ]; then \
+ country=""; \
+ $(install_dir) debian/tmp/usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/html; \
+ else \
+ $(install_dir) debian/tmp/usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/$$country/html; \
+ fi; \
+ $(install_file) $$i/html/manual/*.html debian/tmp/usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/$$country/html; \
+ $(install_file) $$i/html/manual/*.htm debian/tmp/usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/$$country/html; \
+ $(install_file) $$i/signatures.jpg debian/tmp/usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/$$country/html; \
+ $(install_file) $$i/manual.ps debian/tmp/usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/$$country; \
+ $(install_file) $$i/manual.txt debian/tmp/usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/$$country; \
+ done;
+ # jade started calling HTML files '.htm' - generate an index.html link
+ for i in $$(find debian/tmp/usr/share/doc/gnupg-doc/ -name book1.htm); do \
+ ln -s book1.htm $$(dirname $$i)/index.html; \
+ done
+
+ ## pgp2x
+ $(install_dir) debian/tmp/usr/share/doc/gnupg-doc/pgp2x; \
+ for j in pgp2x/*; do \
+ country=$$(basename $$j) ; \
+ if [ $$country = "en" ]; then country=""; else \
+ country="$$country"/; \
+ $(install_dir) debian/tmp/usr/share/doc/gnupg-doc/pgp2x/$$country; \
+ fi; \
+ make DESTDIR=$$(pwd)/debian/tmp/usr/share/doc/gnupg-doc/pgp2x/$$country -C $$j install; \
+ done
+
+ ## mini-howto
+ $(install_dir) debian/tmp/usr/share/doc/gnupg-doc/mini-HOWTO/
+ for i in mini_howto/*; do \
+ country=$$(basename $$i); \
+ if [ "$$country" = "en" ]; then \
+ country=""; \
+ else \
+ mkdir debian/tmp/usr/share/doc/gnupg-doc/mini-HOWTO/$$country; \
+ fi; \
+ $(install_file) $$i/*.html debian/tmp/usr/share/doc/gnupg-doc/mini-HOWTO/$$country; \
+ for type in txt ps html htm; do \
+ if [ ! -z "$$(find $$i -name \*\.$$type)" ]; then \
+ cp $$i/*.$$type debian/tmp/usr/share/doc/gnupg-doc/mini-HOWTO/$$country; \
+ fi; \
+ done; \
+ done;
+
+ $(install_file) debian/changelog debian/tmp/usr/share/doc/gnupg-doc/changelog.Debian
+ find debian/tmp/usr/share/doc/gnupg-doc/ -type f ! -name \*.html \
+ -a ! -name \*.htm -a ! -name \*.jpg| xargs gzip -9
+ $(install_file) debian/copyright debian/tmp/usr/share/doc/gnupg-doc/
+
+ $(install_dir) debian/tmp/usr/share/doc-base/
+ for i in debian/doc-base-*; do \
+ $(install_file) $$i debian/tmp/usr/share/doc-base/$$(basename $$i | sed -e s/doc-base-//); \
+ done
+
+ dpkg-gencontrol -isp
+ chown -R root.root debian/tmp
+ chmod -R go=rX debian/tmp
+ dpkg --build debian/tmp ..
+
+define checkdir
+ test -f gph/en/manual.sgml -a -f debian/rules
+endef
+
+# Below here is fairly generic really
+
+binary: binary-indep binary-arch
+
+checkroot:
+ $(checkdir)
+ test root = "`whoami`"
+
+.PHONY: binary binary-arch binary-indep clean checkroot
Propchange: gnupg-doc/trunk/debian/rules
------------------------------------------------------------------------------
svn:executable = *
Added: gnupg-doc/trunk/gph/Makefile.am
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/gph/Makefile.am?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/gph/Makefile.am (added)
+++ gnupg-doc/trunk/gph/Makefile.am Fri May 8 09:00:27 2009
@@ -1,0 +1,4 @@
+
+SUBDIRS = common en es de fr it ru
+EXTRA_DIST = TODO db2any docbook2texi.patch COPYING.DOC
+
Added: gnupg-doc/trunk/gph/configure.in
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/gph/configure.in?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/gph/configure.in (added)
+++ gnupg-doc/trunk/gph/configure.in Fri May 8 09:00:27 2009
@@ -1,0 +1,75 @@
+dnl
+dnl Configure script source for the GNU Privacy Handbook
+dnl
+dnl (Process this file with autoconf to produce a configure script.)
+AC_REVISION($Revision: 1.9 $)dnl
+AC_PREREQ(2.13)
+
+AC_INIT(en/manual.sgml)
+AM_CONFIG_HEADER(config.h)
+
+dnl
+dnl The version number goes here
+dnl
+AM_INIT_AUTOMAKE(gph,0.3.1)
+
+AM_MAINTAINER_MODE
+
+dnl
+dnl Checks for programs
+dnl
+
+GPH_PROG_DB2ANY
+
+
+dnl
+dnl Checks for libraries
+dnl
+
+
+dnl
+dnl Checks for header files
+dnl
+
+
+dnl
+dnl Checks for typedefs and structures
+dnl
+
+dnl
+dnl Checks for compiler features
+dnl
+
+dnl
+dnl Checks for library functions
+dnl
+
+
+dnl
+dnl Checks for system services
+dnl
+
+if test "$working_db2any" != "yes" ; then
+ AC_MSG_ERROR([[
+***
+*** Due to missing programs it might not be possible to build this package.
+*** For your convenience some rendered versions of documention has
+*** already been build for you and distributed as part of this
+*** package. Please use the versions from the correspondig
+*** language subdirectory.
+*** We apologize for his inconvenience,
+*** Your GPH project team
+***]])
+fi
+
+AC_OUTPUT([
+Makefile
+common/Makefile
+en/Makefile
+es/Makefile
+de/Makefile
+fr/Makefile
+it/Makefile
+ru/Makefile
+])
+
Added: gnupg-doc/trunk/gph/db2any
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/gph/db2any?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/gph/db2any (added)
+++ gnupg-doc/trunk/gph/db2any Fri May 8 09:00:27 2009
@@ -1,0 +1,491 @@
+#!/bin/sh
+# db2any - Docbook to html/ps/info rendering
+#
+# Copyright (C) 2000, 2001 Free Software Foundation, Inc
+#
+# This is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
+#
+# Note: This requires a Posix shell
+#
+# $Id: db2any,v 1.5 2001/04/27 16:08:40 werner Exp $
+
+
+pgm="db2any"
+version="0.7.2"
+
+usage () {
+ echo 'usage: db2any [--help] [options] filename' >&2
+ exit 1
+}
+
+show_banner () {
+ cat <<EOF
+$pgm $version
+Copyright (C) 2001 Free Software Foundation, Inc.
+This is free software; see the source for copying conditions. There is NO
+warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+
+EOF
+}
+
+show_help () {
+ show_banner
+ cat <<EOF
+usage: db2any [options] docbookfile
+
+Options:
+ --mode select the mode (one of: ${all_modes})
+ --help
+ --nosplit
+ --copyfiles
+ --systemcheck
+ --verbose
+ --draft
+ --manvolume n
+ --usestyle file
+ --ignore-xref [not yet implemented]
+
+EOF
+ exit 0
+}
+
+# a list of all possible stylesheet locations
+stylesheet_dirs='
+/usr/local/lib/dsssl/stylesheets/docbook
+/usr/local/share/dsssl/stylesheets/docbook
+/usr/local/lib/sgml/stylesheet/dsssl/docbook/nwalsh
+/usr/local/share/sgml/stylesheet/dsssl/docbook/nwalsh
+/usr/lib/dsssl/stylesheets/docbook
+/usr/share/dsssl/stylesheets/docbook
+/usr/lib/sgml/stylesheet/dsssl/docbook/nwalsh
+/usr/share/sgml/stylesheet/dsssl/docbook/nwalsh
+/usr/lib/sgml/stylesheets/nwalsh-modular
+/usr/share/sgml/stylesheets/nwalsh-modular
+/usr/share/sgml/docbook/stylesheet/dsssl/modular
+'
+
+all_modes="check tex html man texinfo"
+input=
+verbose=no
+draft=no
+nosplit=no
+copyfiles=no
+systemcheck_only=no
+mode=none
+manvolume="man"
+usestyle=""
+expected_args=1
+ignore_xref=no
+while test "`echo $1 | head -c1`" = "-"; do
+ case $1 in
+ --version)
+ echo "$pgm $version"
+ exit 0
+ ;;
+ --help|-h|-help)
+ show_help
+ exit 0
+ ;;
+ --nosplit)
+ nosplit=yes
+ ;;
+ --copyfiles)
+ copyfiles=yes
+ ;;
+ --systemcheck)
+ systemcheck_only=yes
+ expected_args=0
+ ;;
+ --mode)
+ shift
+ if [ $# = 0 ]; then
+ echo "$pgm: missing argument for --mode" >&2
+ exit 1
+ fi
+ mode="$1"
+ ;;
+ --manvolume)
+ shift
+ if [ $# = 0 ]; then
+ echo "$pgm: missing argument for --manvolume" >&2
+ exit 1
+ fi
+ manvolume="$1"
+ ;;
+ --usestyle)
+ shift
+ if [ $# = 0 ]; then
+ echo "$pgm: missing argument for --usestyle" >&2
+ exit 1
+ fi
+ usestyle="$1"
+ ;;
+ --verbose)
+ verbose=yes
+ ;;
+ --draft)
+ draft=yes
+ ;;
+ --ignore-xref)
+ ignore_xref=yes
+ ;;
+ --)
+ shift
+ break
+ ;;
+ *)
+ echo "$pgm: invalid option $1" >&2
+ exit 1
+ ;;
+ esac
+ shift
+done
+
+if [ $# = $expected_args ]; then
+ if [ $# = 1 ]; then
+ input="$1"
+ fi
+else
+ usage
+fi
+
+# check the mode
+case "$mode" in
+ html|HTML)
+ mode=html
+ ;;
+ tex|TEX|TeX|dvi)
+ mode=dvi
+ ;;
+ man|MAN)
+ mode=man
+ ;;
+ texi|TEXI|texinfo|TEXINFO)
+ mode=texinfo
+ ;;
+ check)
+ ;;
+ none)
+ if [ $systemcheck_only != yes ]; then
+ echo "$pgm: no mode specified; use one of: ${all_modes}" >&2
+ exit 1
+ fi
+ ;;
+ *)
+ echo "$pgm: invalid mode $mode" >&2
+ echo "$pgm: valid modes are: ${all_modes}" >&2
+ exit 1
+ ;;
+esac
+
+if [ -n $usestyle ]; then
+ if [ ! -f $usestyle ]; then
+ echo "$pgm: cannot access local stylesteet" >&2
+ exit 1
+ fi
+fi
+
+#######################################
+# Options are all parsed here #
+#######################################
+
+# check whether the given program is availbale in the path
+check_prog () {
+ tmp="$1"
+ save_ifs="$IFS"; IFS=":"
+ for i in $PATH; do
+ test -z "$i" && i=.
+ if test -f $i/$tmp; then
+ IFS="$save_ifs"
+ return 0
+ fi
+ done
+ IFS="$save_ifs"
+ return 1
+}
+
+
+# Figure out all what we need to know about the system we are
+# running on and where the Docbook tools are installed.
+# Tell about it when running in verbose mode.
+do_systemcheck () {
+ # look for Jade
+ jade_version=`jade -v </dev/null 2>&1 | \
+ sed -n 's/.*:I:.*Jade version "\([0-9.]*\)"/\1/p'`
+ if [ -z "$jade_version" ]; then
+ echo "$pgm: error: jade not found" >&2
+ exit 1
+ fi
+ [ $verbose = yes ] && echo "$pgm: Jade version $jade_version found" >&2
+
+ # look for JadeTeX
+ if ! jadetex -v 2>/dev/null | grep -q 'TeX' ; then
+ echo "$pgm: error: jadetex not found" >&2
+ exit 1
+ fi
+
+ # look for the docbook-to-man script. Fixme: we should check that it
+ # it is a recent version.
+ if ! docbook-to-man 2>&1 | grep -q '^usage' ; then
+ echo "$pgm: error: docbook-to-man not found" >&2
+ exit 1
+ fi
+ [ $verbose = yes ] && echo "$pgm: docbook-to-man found" >&2
+
+ # look for the docbook-to-texi scripts.
+ if ! check_prog docbook2texi ; then
+ echo "$pgm: error: docbook2texi not found" >&2
+ exit 1
+ fi
+ [ $verbose = yes ] && echo "$pgm: docbook2texi found" >&2
+ if ! sgml2xml -v /dev/null 2>&1 | grep 'SP version' >/dev/null 2>&1 ; then
+ echo "$pgm: error: sgml2xml not found" >&2
+ exit 1
+ fi
+ [ $verbose = yes ] && echo "$pgm: sgml2xml found" >&2
+
+ # figure out where our stylesheets are
+ tex_stylesheet=none
+ for d in ${stylesheet_dirs}; do
+ file=${d}/print/docbook.dsl
+ if [ -f $file ]; then
+ tex_stylesheet=$file
+ break
+ fi
+ done
+ [ $verbose = yes ] && echo "$pgm: TeX stylesheet: ${tex_stylesheet}" >&2
+ html_stylesheet=none
+ for d in ${stylesheet_dirs}; do
+ file=${d}/html/docbook.dsl
+ if [ -f $file ]; then
+ html_stylesheet=$file
+ break
+ fi
+ done
+ [ $verbose = yes ] && echo "$pgm: HTML stylesheet: ${html_stylesheet}" >&2
+ if [ $tex_stylesheet = none -o $html_stylesheet = none ]; then
+ echo "$pgm: error: stylesheets not found" >&2
+ exit 1
+ fi
+
+}
+
+
+# Render the docbook as HTML
+render_html () {
+ output="`basename $input| sed 's/\.sgml$//'`.html"
+
+ if [ -n "$usestyle" ]; then
+ tmpstyle="`pwd`/`basename $usestyle`-html.tmp"
+ if [ ! -f $tmpstyle -o $usestyle -nt $tmpstyle ]; then
+ sed "s%@DOCBOOK_DSL@%$html_stylesheet%" $usestyle > $tmpstyle
+ fi
+ else
+ tmpstyle="$tex_stylesheet"
+ fi
+
+
+ # --nosplts creates just one HTML file
+ if test $nosplit = yes; then
+ echo "running jade on '$input' ..." >&2
+ jade -d $tmpstyle -t sgml -i html -V nochunks $input > $output
+ echo "$output created"
+ return 0
+ fi
+
+ # Make sure that we have a html subdir
+ if test -d html ; then
+ :
+ else
+ if mkdir html; then
+ echo "'html' directory created" >&2
+ else
+ echo "failed to create 'html' directory" >&2
+ exit 1
+ fi
+ fi
+
+ outputdir="html/`basename $input| sed 's/\.sgml$//'`"
+
+ if test -d $outputdir ; then
+ :
+ else
+ if mkdir $outputdir; then
+ echo "'$outputdir' created" >&2
+ else
+ echo "failed to create '$outputdir'" >&2
+ exit 1
+ fi
+ fi
+ echo "creating html pages in '$outputdir' ..." >&2
+ if test "$input" = "`basename $input`"; then
+ inp="../../$input"
+ else
+ inp="$input"
+ fi
+
+ [ $verbose = yes ] && echo "running jade on '$inp' ..." >&2
+ (cd $outputdir && jade -t sgml -i html -d $tmpstyle $inp )
+ [ $verbose = yes ] && echo "html version in '$outputdir' created" >&2
+
+ # break out all filerefs and copy them to the outputdirectory
+ # fixme: handling of path components is wrong
+ if test $copyfiles = yes; then
+ echo "looking for filerefs ..." >&2
+ for file in `nsgmls -i html $input \
+ | awk '/^AFILEREF[ \t]+CDATA/ {print $3}'`; do
+ d=$outputdir/`basename $file`
+ if cat $file > $outputdir/`basename $file` ; then
+ echo " $file -> $d" >&2
+ fi
+ done
+ fi
+
+ mainfile=`ls $outputdir/${doctype}* | head -1`
+
+ # create a html index file for it, so that we can more easy
+ # find the rendred pages
+ cat > $output <<EOF
+<html><title>$output</title>
+<body>
+
+<a href="$mainfile">$mainfile</a>
+
+</body>
+</html>
+EOF
+
+ [ $verbose = yes ] && echo "$output created with link to '$mainfile'" >&2
+}
+
+
+# This function expects the source file in $texfile and
+# the name of the logfle in $logfile
+run_jadetex () {
+ [ -f $logfile ] && rm $logfile
+ jadetex $texfile
+ if ! tail $logfile | grep -q '^Output written on'; then
+ echo "JadeTeX failed" >&2
+ exit 1
+ fi
+}
+
+# Render the docbook to DVI
+render_dvi () {
+ output="`basename $input| sed 's/\.sgml$//'`.dvi"
+ texfile="`basename $input| sed 's/\.sgml$//'`.tex"
+ logfile="`basename $input| sed 's/\.sgml$//'`.log"
+ auxfile="`basename $input| sed 's/\.sgml$//'`.aux"
+
+ if [ -n "$usestyle" ]; then
+ tmpstyle="`basename $usestyle`-tex.tmp"
+ if [ ! -f $tmpstyle -o $usestyle -nt $tmpstyle ]; then
+ sed "s%@DOCBOOK_DSL@%$tex_stylesheet%" $usestyle > $tmpstyle
+ fi
+ else
+ tmpstyle="$tex_stylesheet"
+ fi
+ [ $verbose = yes ] && echo "running jade on '$input' ..." >&2
+ jade -t tex -i tex -d $tmpstyle $input
+ if ! tail $texfile | grep -q '\\endFOT{}'; then
+ echo "Jade failed" >&2
+ exit 1
+ fi
+
+ # Better delete the aux file first
+ [ -f $auxfile ] && rm $auxfile
+ # The first run won't get the references right, so we have to
+ # run it 2 or 3 times. JadeTex doesn't indicate whether a third
+ # run is required, so we do it always.
+ run_jadetex
+ if [ $draft = no ]; then
+ if tail -100 $logfile \
+ | grep -q '^LaTeX Warning: There were undefined references'; then
+ echo 'running JadeTeX a second and third 2time' >&2
+ run_jadetex
+ run_jadetex
+ fi
+ fi
+
+ [ $verbose = yes ] && echo "$output created as '$output'" >&2
+}
+
+# Render the docbook to troff
+render_man () {
+ output="`basename $input| sed 's/\.sgml$//'`.$manvolume"
+
+ [ $verbose = yes ] && echo "running docbook-to-man on '$input' ..." >&2
+ docbook-to-man $input > $output
+ [ $verbose = yes ] && echo "man page '$output' created" >&2
+}
+
+# Render the docbook to texinfo
+render_texinfo () {
+ output="`basename $input| sed 's/\.sgml$/.texi/'`"
+ tmpxml="`basename $input| sed 's/\.sgml$/.xml/'`"
+
+ [ $verbose = yes ] && echo "running sgml2xml on '$input' ..." >&2
+ sgml2xml -x lower $input > $tmpxml
+ [ $verbose = yes ] && echo "running docbook2texi on '$tmpxml' ..." >&2
+ docbook2texi $tmpxml | sed 's,--,---,' >$output
+ rm $tmpxml
+ [ $verbose = yes ] && echo "man page '$output' created" >&2
+
+}
+
+#######################################
+# main function #
+#######################################
+
+do_systemcheck
+[ $systemcheck_only = yes ] && exit 0
+
+if [ ! -f "$input" ]; then
+ input="$input.sgml"
+ if [ ! -f "$input" ]; then
+ echo "$pgm: '$input': no such file" >&2
+ exit 1
+ fi
+fi
+
+# grep the document type
+doctype=`grep -i '\<doctype' $input|awk 'NR==1 {print $2}'| tr '[A-Z]' '[a-z]'`
+if test -z "$doctype"; then
+ echo "$pgm: error: no DOCTYPE declaration found" >&2
+ exit 1
+fi
+[ $verbose = yes ] && echo "$input: DOCTYPE is '$doctype'" >&2
+
+case $mode in
+ check)
+ nsgmls -vs $input
+ exit $?
+ ;;
+ html)
+ render_html
+ ;;
+ dvi)
+ render_dvi
+ ;;
+ man)
+ render_man
+ ;;
+ texinfo)
+ render_texinfo
+ ;;
+esac
+
+
+exit 0
Propchange: gnupg-doc/trunk/gph/db2any
------------------------------------------------------------------------------
svn:executable = *
Added: gnupg-doc/trunk/gph/es/c3.sgml
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/gph/es/c3.sgml?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/gph/es/c3.sgml (added)
+++ gnupg-doc/trunk/gph/es/c3.sgml Fri May 8 09:00:27 2009
@@ -1,0 +1,982 @@
+<chapter id="management" xreflabel="3">
+<docinfo>
+<date>
+$Id: c3.sgml,v 1.1 2000/02/09 10:29:00 wkoch Exp $
+</date>
+</docinfo>
+<title>
+Gestión de Claves
+</title>
+
+<para>
+En criptografía de clave pública la manipulación de claves es un punto flaco
+a tener en cuenta.
+Un «escucha» podría manipular los ficheros con las claves, o
+falsificar la clave pública y hacerla pública para que la usaran otros como
+si fuera la auténtica.
+Por ejemplo, supongamos que Jordi quisiera monitorizar los mensajes que
+Javier envía a Arancha.
+Jordi podría montar lo que se conoce como un
+<firstterm>intermediario</firstterm> en el plan de ataque.
+En este ataque Jordi crea una nuevo par de claves pública y privada,
+reemplazando la clave pública de Arancha que posee Javier con la nueva clave
+pública.
+A partir de ahí intercepta los mensajes que Javier envía a Arancha.
+Cada mensaje que intercepte lo descifrará usando la nueva clave privada, lo
+volverá a cifrar con la clave auténtica de Arancha, y reenviará el mensaje
+cifrado a Arancha.
+Así, todos los mensajes que Javier envíe a Arancha pueden ser leídos por
+Jordi.
+</para>
+
+<para>
+Una buena gestión de claves es crucial para asegurarse, no sólo de la
+integridad de nuestros ficheros de claves, sino también de la integridad de
+los anillos de claves de otros.
+El punto central en la gestión de claves en &gnupg; es la noción que hay
+detrás de firmar las claves.
+Firmar las claves tiene dos propósitos principales: nos permite detectar una
+manipulación en nuestros anillos de claves, y nos permite certificar que una
+clave realmente pertenece a la persona cuyo nombre aparece en el
+identificador de usuario de la clave.
+Las firmas de las claves también se usan en un esquema conocido como
+<firstterm>anillo de confianza</firstterm> para hacer extensiva la
+certificación de claves que no han sido firmadas directamente por el usuario,
+sino que han sido firmadas por otros en los que él confía.
+Un usuario responsable que lleve a cabo una buena gestión de claves puede
+contrarrestar los efectos prácticos de la manipulación de claves con &gnupg;.
+</para>
+
+<sect1>
+<title>
+Gestionando nuestro par de claves
+</title>
+
+<para>
+Un par de claves se compone de una clave pública y otra privada.
+Una clave pública se compone de la parte pública de la clave de firmado
+maestra, las partes públicas de las subclaves de firmado y cifrado,
+y de un juego de identificadores de usuario que se usa para asociar la clave
+pública con una persona real.
+Cada una de estas partes contiene datos sobre sí misma.
+Para una clave estos datos constan de su propio identificador, fecha de
+creación, fecha de caducidad, etc...
+Para un identificador de usuario, estos datos constan del nombre de la
+persona a la que identifica, un comentario opcional, y una dirección de
+correo electrónico.
+La estructura de la claves privada es parecida, con la diferencia de que sólo
+contiene las partes privadas de las claves, y que no tiene la información del
+identificador de usuario.
+</para>
+
+<para>
+La opción de la línea de órdenes
+<link linkend="edit-key"><option>--edit-key</option></link>
+se puede usar para ver un par de claves.
+Por ejemplo,
+
+<screen width="80">
+<prompt>jordi%</prompt> <userinput>gpg --edit-key jordi at cat.es</userinput>
+Secret key is available.
+
+pub 1024D/1208DD4F created: 1999-09-24 expires: never trust: -/u
+sub 1024g/B9688D9E created: 1999-09-24 expires: never
+sub 2016G/4D88ACC4 created: 1999-09-26 expires: 2002-09-25
+sub 960D/412EAF0C created: 1999-09-26 expires: 2002-09-25
+(1) Jordi (Castell S.L.) <jordi at cat.es>
+(2) Jordi (oficina) <jordi at castell.com>
+
+<prompt>Command></prompt>
+</screen>
+
+La clave pública se muestra junto con una indicación sobre si la clave privada
+se encuentra disponible o no.
+La información sobre cada componente de la clave pública se da en una lista.
+La primera columna indica el tipo de la clave.
+La palabra clave <literal>pub</literal> identifica a la clave pública maestra
+de firmado, y la palabra clave <literal>sub</literal> identifica a una clave
+pública subordinada a la anterior.
+La segunda columna informa sobre el tamaño en &dquo;bits&dquo; de la clave, el
+tipo, y el identificador.
+El tipo es <literal>D</literal> para una clave DSA, <literal>g</literal> para
+una clave ElGamal que sólo se pueda usar para cifrar, y <literal>G</literal>
+para una clave ElGamal que se pueda usar tanto para cifrar como para firmar.
+La fecha de creación y la fecha de caducidad se muestran en las columnas tres
+y cuatro.
+Los identificadores de usuario aparecen en una lista a continuación de las
+claves.
+</para>
+
+<para>
+Se puede obtener más información sobre la clave mediante órdenes
+interactivas.
+La orden <link linkend="toggle"><command>toggle</command></link> sirve para
+conmutar entre los componentes público y privado de un par de claves, siempre
+y cuando ambos componentes estén presentes.
+
+<screen width="80">
+<prompt>Command></prompt> <userinput>toggle</userinput>
+
+sec 1024D/1208DD4F created: 1999-09-24 expires: never
+sbb 1024g/B9688D9E created: 1999-09-24 expires: never
+sbb 960D/412EAF0C created: 1999-09-26 expires: 2002-09-25
+sbb 2016G/4D88ACC4 created: 1999-09-26 expires: 2002-09-25
+(1) Jordi (Castell S.L.) <jordi at cat.es>
+(2) Jordi (oficina) <jordi at castell.com>
+</screen>
+
+Esta información es parecida a la del componente para la clave pública.
+La palabra clave <literal>sec</literal> identifica a la clave privada maestra
+de firmado, y la palabra clave <literal>sbb</literal> identifica las claves
+subordinadas privadas.
+Los identificadores de usuario de la clave pública también aparecen en este
+caso.
+</para>
+
+<sect2>
+<title id="integrity">
+Integridad de claves
+</title>
+
+<para>
+Al distribuir nuestra clave pública, estamos distribuyendo los componentes
+públicos de nuestras claves maestra y subordinada, así como los
+identificadores de usuario.
+Sin embargo, por sí sola, la distribución de este material constituye un
+riesgo para la seguridad ya que sería posible que un atacante manipulara la
+clave.
+Se puede modificar una clave pública añadiendo o substituyendo claves, o
+añadiendo o cambiando los identificadores de usuario.
+Al manipular un identificador de usuario, el atacante podría cambiar la
+dirección de correo del identificador de usuario y redireccionar así el
+correo a su propia dirección.
+Al cambiar una de las claves de cifrado el atacante también podría descifrar
+los mensajes que le llegaran redireccionados.
+</para>
+
+<para>
+El uso de las firmas digitales es una solución a este problema.
+Cuando unos datos son firmados por una clave privada, la clave pública
+correspondiente queda ligada a los datos firmados.
+En otras palabras, sólo la clave pública correspondiente puede verificar la
+firma y asegurar que los datos no han sido modificados.
+Una clave pública se puede proteger de la manipulación usando su
+correspondiente clave privada maestra, y firmando con ésta los componentes de
+la clave pública y los identificadores de usuario, ligando de este modo los
+componentes a la clave pública maestra.
+La acción de firmar los componentes de la clave pública con la
+correspondiente clave privada maestra se conoce como
+<firstterm>autofirmar</firstterm>, y una clave pública que contenga
+identificadores de usuario autofirmados ligados a ella se llama
+<firstterm>certificado</firstterm>.
+</para>
+
+<!--
+%\begin{figure}
+%Blank
+%\caption{This should depict how self-signatures bind information to
+%a public key.}\label{fig:selfsignedkey}
+%\end{figure}
+%
+%As an example, Figure~\ref{fig:selfsignedkey} illustrates Chloe's public
+%key, which has been self-signed to bind the user IDs and public subkeys
+%to the public master key.
+%The signatures on the user IDs can be checked with the \texttt{check}
+%command from the key edit menu.
+-->
+
+<para>
+Como ejemplo, si Jordi tuviera dos identificadores de usuario y tres
+subclaves, las firmas en los identificadores de usuario se podrían comprobar
+con la orden <link linkend="check"><command>check</command></link> desde el
+menú de edición de la clave.
+
+<screen width="80">
+<prompt>jordi%</prompt> <userinput>gpg --edit-key jordi</userinput>
+Secret key is available.
+
+pub 1024D/1208DD4F created: 1999-09-24 expires: never trust: -/u
+sub 1024g/B9688D9E created: 1999-09-24 expires: never
+sub 960D/412EAF0C created: 1999-09-26 expires: 2002-09-25
+sub 2016G/4D88ACC4 created: 1999-09-26 expires: 2002-09-25
+(1) Jordi (Castell S.L.) <jordi at cat.es>
+(2) Jordi (oficina) <jordi at castell.com>
+
+<prompt>Command></prompt> <userinput>check</userinput>
+uid Jordi (Castell S.L.) <jordi at cat.es>
+sig! 1208DD4F 1999-09-24 [self-signature]
+uid Jordi (oficina) <jordi at castell.com>
+sig! 1208DD4F 1999-09-26 [self-signature]
+</screen>
+
+Como era de esperar, la clave firmante para cada firma es la clave de firmado
+maestra con el identificador de clave <literal>0x26B6AAE1</literal>.
+La autofirma en las subclaves se encuentra presente en la clave pública, pero
+en la interfaz de &gnupg; no aparece.
+</para>
+</sect2>
+
+<sect2>
+<title>
+Añadir y eliminar componentes a las claves
+</title>
+
+<para>
+Tanto las nuevas subclaves como los nuevos identificadores de usuario,
+pueden ser añadidos a nuestro par de claves una vez que éste ya haya sido
+creado.
+Un identificador de usuario se añade mediante la orden
+<link linkend="adduid"><command>adduid</command></link>.
+A continuación se nos pedirá que introduzcamos un nombre real, una dirección
+de correo electrónico, y un comentario, del mismo modo que cuando generamos
+el par de claves inicial.
+Una subclave se añade usando la orden
+<link linkend="addkey"><command>addkey</command></link>.
+La interfaz es parecida a la usada cuando generamos un par de claves nuevo.
+La subclave puede ser una clave para firmado DSA y una clave sólo para cifrado
+ElGamal, o una clave para firmado y cifrado ElGamal.
+Cuando se genera una subclave o un identificador de usuario, éstos son
+autofirmados con nuestra clave de firmado maestra, por lo que se nos
+requerirá que introduzcamos la contraseña.
+</para>
+
+<para>
+Los identificadores de usuario adicionales son útiles si necesitamos
+múltiples identidades.
+Por ejemplo, puede darse el caso de que utilicemos una identidad para el
+trabajo y otra para nuestras actividades políticas.
+Los colegas de trabajo nos conocerán por nuestro identificador de usuario del
+trabajo.
+Los correligionarios políticos nos conocerán por nuestra identidad de usuario
+política.
+Como es posible que estos grupos de personas no coincidan, cada grupo no se
+fiará del identificador que no corresponda.
+Por lo tanto, ambos identificadores de usuario son necesarios.
+</para>
+
+<para>
+Las subclaves adicionales son también muy útiles.
+Los identificadores de usuario asociados con nuestra clave pública maestra
+son validados por las personas con quien nos comunicamos y por tanto, cambiar
+la clave maestra requiere «recertificación».
+Pero esto puede resultar difícil y una pérdida de tiempo si nos comunicamos
+con muchas personas.
+Por otra parte, es bueno cambiar las subclaves de cifrado periódicamente.
+Si una clave es descubierta, todos los datos cifrados con esa clave serán
+vulnerables.
+De todos modos, al cambiar las claves sólo los datos cifrados con la clave
+descubierta serán revelados.
+</para>
+
+<para>
+También es posible eliminar las subclaves y los identificadores de usuario.
+Para eliminar una subclave o un identificador de usuario es preciso
+seleccionarlo primero con las órdenes
+<link linkend="key"><command>key</command></link> o
+<link linkend="uid"><command>uid</command></link> respectivamente.
+Estas órdenes actúan como conmutadores.
+Por ejemplo, la orden <command>key <parameter>2</parameter></command>
+selecciona la segunda subclave, e invocando
+<command>key <parameter>2</parameter></command> de nuevo, desactiva la
+selección.
+Si no se da ningún otro argumento extra, todas las subclaves o
+identificadores de usuario son deseleccionados.
+Una vez que los identificadores de usuario que se van a eliminar son
+seleccionados, la orden
+<link linkend="deluid"><command>deluid</command></link>
+elimina los identificadores de usuario de la clave.
+De igual forma, la orden
+<link linkend="delkey"><command>delkey</command></link>
+elimina todas las subclaves previamente seleccionadas de nuestras claves
+pública y privada.
+</para>
+
+<para>
+En la gestión local de anillos de claves, el eliminar componentes
+innecesarios de una clave es una buena práctica para aliviar los anillos de
+claves públicas de otros.
+Sin embargo, eliminar identificadores de usuarios y subclaves de nuestra
+propia clave no es siempre conveniente, ya que puede complicar la
+distribución de la clave.
+Por definición, cuando un usuario importa nuestra clave pública actualizada
+ésta se fusiona con la copia de la clave pública vieja en su anillo de
+claves, siempre que la vieja esté allí «a priori».
+Los componentes de ambas claves se combinan con la fusión, y el resultado de
+ésta es que se añade cualquier nuevo componente, pero también que se
+restaura cualquier componente eliminado.
+Para actualizar de manera correcta la clave es necesario que el usuario
+elimine primero la versión antigua de nuestra clave, y después que importe la
+versión nueva.
+Esto significa una carga extra para la gente con la que nos comunicamos.
+Es más, si enviáramos nuestra clave a un servidor de claves la fusión
+ocurriría a nuestro pesar, y cualquiera que se bajara nuestra clave del
+servidor no vería nunca nuestra clave con los componentes eliminados.
+En consecuencia, para actualizar nuestra propia clave es mejor revocar los
+componentes de la clave que eliminarlos.
+</para>
+</sect2>
+
+<sect2>
+<title>
+Revocar componentes de una clave
+</title>
+
+<para>
+Para revocar una subclave antes tenemos que seleccionarla.
+Una vez seleccionada, puede ser revocada con la orden
+<link linkend="revkey"><command>revkey</command></link>.
+La clave se revoca añadiéndole una autofirma de revocación.
+Al contrario que la opción de la línea de órdenes
+<option>--gen-revoke</option>, el efecto de revocación de una subclave es
+inmediato.
+</para>
+
+<screen width="80">
+
+<prompt>Command></prompt> <userinput>key</userinput> <parameter>4D88ACC4</parameter>
+
+pub 1024D/1208DD4F created: 1999-09-24 expires: never trust: -/u
+sub 1024g/B9688D9E created: 1999-09-24 expires: never
+sub* 2016G/4D88ACC4 created: 1999-09-26 expires: 2002-09-25
+sub 960D/412EAF0C created: 1999-09-26 expires: 2002-09-25
+(1) Jordi (Castell S.L.) <jordi at cat.es>
+(2) Jordi (oficina) <jordi at castell.com>
+
+<prompt>Command></prompt> <userinput>revkey</userinput>
+Do you really want to revoke this key? y
+
+You need a passphrase to unlock the secret key for
+user: "Jordi (Castell S.L.) <jordi at cat.es>"
+1024-bit DSA key, ID 1208DD4F, created 1999-09-24
+
+pub 1024D/1208DD4F created: 1999-09-24 expires: never trust: -/u
+sub 1024g/B9688D9E created: 1999-09-24 expires: never
+sub 2016G/4D88ACC4 created: 1999-09-26 expires: 2002-09-25
+rev! subkey has been revoked: 1999-09-26
+sub 960D/412EAF0C created: 1999-09-26 expires: 2002-09-25
+(1) Jordi (Castell S.L.) <jordi at cat.es>
+(2) Jordi (oficina) <jordi at castell.com>
+</screen>
+
+<para>
+La revocación de un identificador de usuario funciona de modo diferente.
+Generalmente, un identificador de usuario recolecta firmas que atestigüen que
+el identificador de usuario describe a la persona que sea la auténtica
+propietaria de la clave asociada.
+En teoría un identificador de usuario describe a una persona para siempre,
+ya que la identidad de esa persona no cambiará nunca.
+En la práctica los elementos del identificador de usuario, como la dirección
+de correo electrónico y el comentario, pueden cambiar con el tiempo,
+invalidando así el identificador de usuario.
+</para>
+
+<para>
+Las especificaciones de OpenPGP
+<comment>Primera referencia a OpenPGP</comment>
+no preveen la revocación del identificador de usuario, pero un identificador
+de usuario puede ser revocado de modo efectivo, revocando la autofirma en el
+identificador de usuario.
+Por razones de seguridad descritas
+<link linkend="integrity">anteriormente</link>, los corresponsales no
+confiarán en un identificador de usuario con una autofirma no válida.
+</para>
+
+<para>
+Una firma puede ser revocada mediante la orden
+<link linkend="revsig"><command>revsig</command></link>.
+Como es posible que hayamos firmado cualquier cantidad de identificadores de
+usuario, la interfaz nos pedirá que decidamos si queremos o no revocar cada
+una de las firmas.
+</para>
+
+<screen width="80">
+<prompt>Command></prompt> <userinput>revsig</userinput>
+Command> revsig
+You have signed these user IDs:
+ Jordi (Castell S.L.) <jordi at cat.es>
+ signed by 1208DD4F at 1999-09-24
+ Jordi (oficina) <jordi at castell.com>
+ signed by 1208DD4F at 1999-09-26
+user ID: "Jordi (Castell S.L.) <jordi at cat.es>"
+signed with your key 1208DD4F at 1999-09-24
+Create a revocation certificate for this signature? (y/N)n
+user ID: "Jordi (oficina) <jordi at castell.com>"
+signed with your key 1208DD4F at 1999-09-26
+Create a revocation certificate for this signature? (y/N)y
+You are about to revoke these signatures:
+ Jordi (oficina) <jordi at castell.com>
+ signed by 1208DD4F at 1999-09-26
+Really create the revocation certificates? (y/N)y
+
+You need a passphrase to unlock the secret key for
+user: "Jordi (Castell S.L.) <jordi at cat.es>"
+1024-bit DSA key, ID 1208DD4F, created 1999-09-24
+
+Enter passphrase:
+
+pub 1024D/1208DD4F created: 1999-09-24 expires: never trust: -/u
+sub 1024g/B9688D9E created: 1999-09-24 expires: never
+sub 2016G/4D88ACC4 created: 1999-09-26 expires: 2002-09-25
+rev! subkey has been revoked: 1999-09-26
+sub 960D/412EAF0C created: 1999-09-26 expires: 2002-09-25
+(1) Jordi (Castell S.L.) <jordi at cat.es>
+(2) Jordi (oficina) <jordi at castell.com>
+</screen>
+
+<para>
+Un identificador de usuario revocado vendrá indicado por la firma de
+revocación en el identificador, y se podrá ver en las firmas en la lista de
+identificadores de usuario de las claves.
+</para>
+
+<screen width="80">
+<prompt>Command<</prompt> <userinput>check</userinput>
+uid Jordi (Castell S.L.) <jordi at cat.es>
+sig! 1208DD4F 1999-09-24 [self-signature]
+uid Jordi (oficina) <jordi at castell.com>
+rev! 1208DD4F 1999-09-26 [revocation]
+sig! 1208DD4F 1999-09-26 [self-signature]
+sig! B87DBA93 1999-06-28 [self-signature]
+</screen>
+
+<para>
+Al revocar tanto las subclaves como las autofirmas en los identificadores de
+usuarios, añadimos autofirmas de revocación a la clave.
+Ya que las firmas son añadidas a la clave y no eliminamos nada, una
+revocación siempre estará visible para otros usuarios desde el momento en el
+que la actualización de nuestra clave pública sea distribuida y fusionada con
+las copias más viejas de ésta.
+Por lo tanto, la revocación garantiza que todos los usuarios tengan una copia
+consistente de nuestra clave pública.
+</para>
+</sect2>
+
+<sect2>
+<title>
+Actualizar la fecha de caducidad de una clave
+</title>
+
+<para>
+La fecha de caducidad de una clave puede ser actualizada con la orden
+<link linkend="expire"><command>expire</command></link>
+desde el menú de edición de la clave.
+Si no se selecciona ninguna clave, se actualizará la fecha de caducidad de la
+clave primaria.
+De otro modo, se actualizará la fecha de caducidad de la clave subordinada
+que hayamos seleccionado.
+</para>
+
+<para>
+La fecha de caducidad de una clave está asociada con la autofirma de la
+clave.
+La fecha de caducidad se actualiza eliminando la autofirma antigua y
+añadiendo una nueva autofirma.
+Ya que los corresponsales no habrán eliminado la autofirma antigua, verán una
+autofirma adicional en la clave cuando actualicen su copia de nuestra clave.
+La última autofirma es la que tiene precedencia, así que todos los
+corresponsales pueden saber sin ambigüedad las fechas de caducidad de
+nuestras claves.
+</para>
+</sect2>
+</sect1>
+
+<sect1>
+<title>
+Validar otras claves en nuestro anillo de claves públicas
+</title>
+
+<para>
+En el capítulo <xref linkend="intro"> se introdujo un procedimiento para
+validar las claves públicas de otros usuarios: la clave de otro usuario se
+valida comprobando personalmente la huella digital de su clave, y firmando su
+clave pública con nuestra clave privada.
+Comprobando personalmente la huella digital podemos estar seguros de que la
+clave pertenece realmente al supuesto usuario y, dado que hemos firmado la
+clave, podemos estar seguros de que detectaremos cualquier manipulación o
+falsificación en un futuro.
+Desafortunadamente este proceso se complicado cuando debemos validar un gran
+número de claves o cuando debemos comunicarnos con personas a las que no
+conocemos personalmente.
+</para>
+
+<para>
+&Gnupg; trata este problema con un mecanismo conocido como
+<firstterm>anillo de confianza</firstterm>.
+En el modelo del anillo de confianza la responsabilidad de la validación de
+las claves públicas recae en las personas en las que confiamos.
+Por ejemplo, supongamos que
+<itemizedlist spacing="compact">
+<listitem>
+<para>
+Javier ha firmado la clave de Arancha y que,
+</para>
+</listitem>
+<listitem>
+<para>
+Arancha ha firmado las claves de Jordi y de Ignacio.
+</para>
+</listitem>
+</itemizedlist>
+
+Si Javier confía en Arancha lo suficiente como para validar las claves que él
+firma, entonces Javier puede deducir que las claves de Jordi y de Ignacio son
+válidas sin llegar a comprobarlas personalmente.
+Javier se limitará a usar su copia validada de la clave pública de Arancha para
+comprobar que las firmas de Arancha sobre Jordi e Ignacio son auténticas.
+Por lo general, y asumiendo que Javier confíe plenamente en todos como para
+validar las claves que firmen, cualquier clave firmada por una clave válida
+también es considerada válida.
+El origen es la clave de Javier, que se asumirá axiomáticamente como válida.
+</para>
+
+<sect2>
+<title>
+Confianza en el propietario de una clave
+</title>
+
+<para>
+En la práctica la confianza es algo subjetivo.
+Por ejemplo, la clave de Arancha es válida para Javier ya que ha sido firmada
+por ella, pero Javier puede desconfiar de otras claves que hayan sido
+validadas por la firma de Arancha.
+En este caso, Javier no aceptaría las claves de Jordi e Ignacio como válidas
+sólo porque hayan sido firmadas por Arancha.
+El modelo del anillo de confianza prevee este caso mediante un indicador que
+asocia nuestro nivel de confianza en el propieario de la clave, a cada clave
+pública en nuestro anillo de claves.
+Existen cuatro niveles de confianza:
+
+<variablelist>
+<varlistentry>
+<term>
+unknown
+</term>
+<listitem>
+<para>
+Desconocido.
+No se sabe nada sobre el dueño de la clave firmante.
+Las claves en nuestro anillo de claves que no nos pertenezcan tendrán al
+principio este nivel de confianza.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>
+none
+</term>
+<listitem>
+<para>
+Ninguno.
+Se sabe que el propietario firma otras claves de modo impropio.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>
+marginal
+</term>
+<listitem>
+<para>
+Marginal.
+El propietario comprende las implicaciones de firmar una clave y valida las
+claves de forma correcta antes de firmarlas.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term>
+full
+</term>
+<listitem>
+<para>
+Absoluto.
+El propietario comprende perfectamente las implicaciones de firmar una clave
+y su firma sobre una clave es tan buena como la nuestra.
+</para>
+</listitem>
+</varlistentry>
+</variablelist>
+
+El nivel de confianza en una clave es algo que sólo nosotros podemos asignar
+a la clave, y se considera información privada.
+El nivel de confianza no se exporta con la clave, de hecho no se almacena en
+los anillos de claves sino en una base de datos aparte.
+</para>
+
+<para>
+El editor de claves de &gnupg; puede ser usado para ajustar nuestra confianza
+en el propietario de una clave.
+La orden es <link linkend="trust"><command>trust</command></link>.
+En el siguiente ejemplo Javier edita su confianza en Arancha y actualiza la base
+de datos para recomputar qué claves son válidas, basándose en su nuevo nivel
+de confianza en Arancha.
+
+<screen width="80">
+<prompt>javier:~$</prompt> <userinput>gpg --edit-key Aranzanzu</userinput>
+
+pub 1024D/B63E132C created: 1999-09-24 expires: never trust: q/f
+sub 1024g/581A915F created: 1999-09-24 expires: never
+(1) Ar\xc3\xa1nzazu (A.G.deZ.) <arancha at nav.es>
+
+<prompt>Command></prompt> <userinput>trust</userinput>
+pub 1024D/B63E132C created: 1999-09-24 expires: never trust: q/f
+sub 1024g/581A915F created: 1999-09-24 expires: never
+(1) Ar\xc3\xa1nzazu (A.G.deZ.) <arancha at nav.es>
+
+Please decide how far you trust this user to correctly
+verify other users' keys (by looking at passports,
+checking fingerprints from different sources...)?
+
+ 1 = Don't know
+ 2 = I do NOT trust
+ 3 = I trust marginally
+ 4 = I trust fully
+ s = please show me more information
+ m = back to the main menu
+
+<prompt>Your decision?</prompt> <userinput>3</userinput>
+
+pub 1024D/B63E132C created: 1999-09-24 expires: never trust: m/f
+sub 1024g/581A915F created: 1999-09-24 expires: never
+(1) Ar\xc3\xa1nzazu (A.G.deZ.) <arancha at nav.es>
+
+<prompt>Command></prompt> <userinput>quit</userinput>
+[...]
+</screen>
+
+La confianza en el propietario de la clave y la validez de la clave se
+indican a la derecha al mostrar la clave.
+La confianza en el propietario se muestra primero, y la validez
+después<footnote><para>N. de T.: &Gnupg; hace un uso excesivo de la palabra
+“trust”, utilizándola en el sentido de «confianza en el
+propietario y confianza en la clave».
+Esto puede llevar a confusión.
+Algunas veces la confianza en un propietario viene referida como
+<firstterm>owner-trust</firstterm>
+para distinquirla de la confianza en una clave.
+Sin embargo, a lo largo de este manual “trust” se usa en el
+sentido de «confianza en el propietario de la clave», y
+“validity” en el sentido de «confianza en que una clave
+pertenece a la persona asociada con el identificador de clave».
+</para></footnote>.
+Los cuatro niveles de confianza/validez se encuentran abreviados: unknown
+(<literal>q</literal>), none (<literal>n</literal>), marginal
+(<literal>m</literal>), y full (<literal>f</literal>).
+O sea, <firstterm>desconocido</firstterm>, <firstterm>ninguno</firstterm>,
+<firstterm>marginal</firstterm> y <firstterm>absoluto</firstterm>.
+En este caso, la clave de Arancha es totalmente válida ya que está firmada por
+Javier. Al principio el nivel de confianza que Javier tiene en Arancha es
+desconocido, por lo que no procede validar otras claves;
+pero luego decide confiar en ella de modo marginal.
+</para>
+</sect2>
+
+<sect2>
+<title>
+Usar la confianza para validar las claves
+</title>
+
+<para>
+El anillo de confianza permite usar un algoritmo más elaborado para validar
+una clave.
+Anteriormente, una clave sólo se consideraba válida si la firmábamos
+nosotros personalmente.
+<!-- HERE, math -->
+Ahora es posible usar un algoritmo más flexible: una clave
+<emphasis>K</emphasis> se considera válida si cumple dos condiciones:
+<orderedlist spacing="compact">
+<listitem>
+<para>
+si viene firmada por las suficientes claves válidas, lo que quiere decir
+<itemizedlist spacing="compact">
+<listitem>
+<para>
+que la hemos firmado nosotros personalmente,
+</para>
+</listitem>
+<listitem>
+<para>
+o que ha sido firmada por una clave de plena confianza,
+</para>
+</listitem>
+<listitem>
+<para>
+o que ha sido firmada por tres claves de confianza marginal;
+</para>
+</listitem>
+</itemizedlist>
+</para>
+</listitem>
+<listitem>
+<para>
+<!-- HERE, math -->
+y si el camino de claves firmadas que nos lleva desde <emphasis>K</emphasis>
+hasta nuestra propia clave es de cinco pasos o menos.
+</para>
+</listitem>
+</orderedlist>
+
+La longitud del camino, en número de claves con confianza marginal
+requeridas, y el número de claves con confianza plena requeridas se pueden
+cambiar.
+Los números dados arriba son los valores por definición usados por &gnupg;.
+</para>
+
+<para>
+<xref linkend="wot-examples"> muestra un anillo de confianza cuyo origen está
+en Javier.
+El gráfico ilustra quién ha firmado las claves de quién.
+La tabla muestra qué claves son consideradas válidas por Javier en base a su
+confianza en otros miembros del anillo.
+<comment>Un error potential: <option>--completes-needed</option> en la línea
+de órdenes, parece que es ignorado al combinarlo con
+<option>--update-trustdb</option>.
+Sin embargo, el valor se toma correctamente si se pone en el fichero
+&dquo;options&dquo;.</comment>
+Este ejemplo asume que se necesitan dos claves de confianza marginal o una
+de confianza plena para validar otra clave.
+La longitud máxima del camino es tres.
+</para>
+
+<para>
+Al computar claves válidas en el ejemplo, las de Arancha e Ignacio siempre son
+consideradas como totalmente válidas, ya que están directamente firmadas por
+Javier.
+La validez de las otras claves depende de la confianza.
+En el primer caso la confianza en Ignacio es plena, lo que implica que las
+claves de Jordi y Claudia se considerarán válidas.
+En el segundo ejemplo la confianza en Arancha e Ignacio es marginal.
+Ya que son necesarias dos claves de confianza marginal para dar validez total
+a una clave, la clave de Jordi será considerada como totalmente válida, pero
+la clave de Claudia será considerada sólo como marginalmente válida.
+En el caso en el que Jordi e Ignacio tuvieran confianza marginal, la clave de
+Jordi sería marginalmente válida ya que la clave de Ignacio es totalmente
+válida.
+Sin embargo, la clave de Claudia será considerada marginalmente válida ya que
+sólo se puede usar una clave completamente válida para validar otras claves,
+y la clave de Ignacio es la única clave válida que se ha usado para firmar la
+clave de Claudia.
+Al añadir un nivel de confianza marginal a Arancha, la clave de Jordi se
+convierte en totalmente válida y por tanto puede ser usada para validar
+totalmente la clave de Claudia, y validar marginalmente la clave de Jimena.
+Por último, una confianza plena en Arancha, Jordi y Jimena es todavía
+insuficiente para validar la clave de Gonzalo ya que el camino máximo de
+certificación es tres, pero la longitud del camino desde Gonzalo hasta Javier es
+cuatro.
+</para>
+
+<para>
+El modelo del anillo de confianza es una aproximación flexible al problema
+del intercambio seguro de claves públicas.
+Nos permite poner a punto &gnupg; para que refleje el modo en que lo usamos.
+Es posible llegar a insistir en múltiples caminos cortos desde nuestra clave
+hasta otra clave <emphasis>K</emphasis> para cambiar el nivel de confianza.
+Por otra parte, puede ser que caminos más largos nos satisfagan e incluso
+un sólo camino desde nuestra clave hasta la otra clave
+<emphasis>K</emphasis>.
+El requerimiento de múltiples caminos cortos es una fuerte garantía de que
+<emphasis>K</emphasis> pertenece a quien nosotros creemos.
+El precio, por supuesto, es la dificultad añadida para validar claves, ya que
+debemos firmar personalmente más claves que si aceptáramos menos y más largos
+caminos.
+</para>
+
+<figure id="wot-examples" float=1>
+<title>
+Un anillo de confianza hipotético
+</title>
+<!--
+The graph indicates who has signed who's keys.
+The table, in which names have been abbreviated, shows which keys are
+valid depending on how Alice trusts other members in the web.
+Alice considers different keys valid depending on how she trusts
+the members of the web.
+-->
+
+<mediaobject>
+ <!-- using marked sections here is not the perfect solution but
+ until we have figured out how to modify the stylesheets to
+ prefer one format over another depending on the backend,
+ we can do it this way.
+ The current TeX stylesheet takes only the first imageobject
+ We do mark only the first imageobject so that the mediaobject
+ is valid without requiring to do an nsgmls -i foo.
+ -->
+ <![ %tex; [
+ <imageobject>
+ <imagedata fileref="signatures.eps" format="eps">
+ </imageobject>
+ ]]>
+ <imageobject>
+ <imagedata fileref="signatures.jpg" format="jpg">
+ </imageobject>
+ <textobject>
+ <phrase>A graph indicating who has signed who's key</phrase>
+ </textobject>
+ <textobject>
+ <para>
+ Some longer blurb to verbal describe the excact content
+ of the image. This may be of use for a Braille display.
+ </para>
+ </textobject>
+</mediaobject>
+
+<informaltable frame="all">
+<tgroup cols="4" rowsep="1" colsep="1">
+<colspec colname="one" colnum="1">
+<colspec colname="two" colnum="2">
+<colspec colname="three" colnum="3">
+<colspec colname="four" colnum="4">
+<spanspec spanname="lefthalf" namest="one" nameend="two" align="center">
+<spanspec spanname="righthalf" namest="three" nameend="four" align="center">
+
+<thead>
+<row>
+<entry spanname="lefthalf">trust/confianza</entry>
+<entry spanname="righthalf">validity/validez</entry>
+</row>
+<row>
+<entry align="center">marginal</entry>
+<entry align="center">full/plena</entry>
+<entry align="center">marginal</entry>
+<entry align="center">full/plena</entry>
+</row>
+</thead>
+<tbody>
+<row>
+<entry></entry>
+<entry>Ignacio</entry>
+<entry></entry>
+<entry>Arancha, Jordi, Ignacio, Claudia</entry>
+</row>
+
+<row>
+<entry>Arancha, Ignacio</entry>
+<entry></entry>
+<entry>Claudia</entry>
+<entry>Arancha, Jordi, Ignacio</entry>
+</row>
+
+<row>
+<entry>Jordi, Ignacio</entry>
+<entry></entry>
+<entry>Jordi, Claudia</entry>
+<entry>Arancha, Ignacio</entry>
+</row>
+
+<row>
+<entry>Arancha, Jordi, Ignacio</entry>
+<entry></entry>
+<entry>Jimena</entry>
+<entry>Arancha, Jordi, Ignacio, Claudia</entry>
+</row>
+
+<row>
+<entry></entry>
+<entry>Arancha, Jordi, Jimena</entry>
+<entry></entry>
+<entry>Arancha, Jordi, Jimena, Claudia</entry>
+</row>
+</tbody>
+</tgroup>
+</informaltable>
+</figure>
+</sect2>
+</sect1>
+
+<sect1>
+<title>
+Distribución de claves
+</title>
+
+<para>
+Lo ideal sería que pudiéramos distribuir nuestra clave entregándosela en
+persona a nuestros corresponsales.
+Sin embargo, en la práctica las claves se distribuyen a menudo por correo
+electrónico o algún otro medio de comunicación electrónica.
+La distribución por correo electrónico es una buena práctica sólo cuando
+tengamos unos pocos corresponsales, e incluso si tuviéramos muchos
+corresponsales, podríamos usar un medio alternativo como puede ser publicar
+nuestra clave pública en nuestra página en internet.
+Pero esto es inútil si las personas que necesitan nuestra clave pública no
+saben dónde encontrar nuestra página.
+</para>
+
+<para>
+Para solventar este problema existen los servidores de claves públicas que
+recolectan y distribuyen las claves públicas.
+Cuando un servidor recibe una clave pública, bien la añade a la base de datos
+o bien la fusiona con una copia de la clave.
+Cuando alguien requiere al servidor una clave pública, éste la busca en la
+base de datos y, si la encuentra, la envía a quien se la haya solicitado.
+</para>
+
+<para>
+Los servidores de claves también son útiles cuando hay muchas personas que
+firman las claves de otras con frecuencia.
+Sin un servidor de claves, cuando Arancha firmara la clave de Javier, debería
+enviar a éste una copia de la clave firmada por ella de manera que Javier
+pudiera añadir la clave firmada a su anillo de claves, así como distribuirla a
+todos sus corresponsales.
+Mediante este proceso Javier y Arancha sirven a la totalidad de la comunidad
+construyendo lazos en forma de anillos de confianza o lo que es lo mismo,
+mejorando la seguridad de PGP.
+De todos modos esto es una molestia si se firman las claves con frecuencia.
+</para>
+
+<para>
+El uso de un servidor de claves facilita este proceso.
+Después de firmar la clave de Javier, Arancha puede enviar la copia firmada por
+ella al servidor de claves.
+El servidor de claves añade la firma de Arancha a la copia que ya existente
+de la clave pública de Javier.
+Las personas que estén interesadas en actualizar su copia de la clave de
+Javier consultan al servidor por propia iniciativa para obtener la clave
+actualizada.
+Javier no necesita distribuir la clave y puede obtener las firmas en su clave
+requiriéndolas al servidor.
+<comment>La opción <option>--keyserver</option> debe preceder a las opciones
+<option>--send-key</option> o <option>--recv-key</option>.
+Esto es un error.</comment>
+</para>
+
+<para>
+Se puede enviar una o más claves usando la opción de la línea de órdenes
+<link linkend="send-keys"><option>--send-keys</option></link>.
+Esta opción toma uno o más especificadores de clave, y envía las claves
+especificadas al servidor de claves.
+El servidor al que se envían las claves es especificado con la opción de la
+línea de orden <link linkend="keyserver"><option>--keyserver</option></link>.
+Paralelamente, la opción
+<link linkend="recv-keys"><option>--recv-keys</option></link> se usa para
+obtener claves desde un servidor de claves, pero la opción
+<option>--recv-keys</option> requiere el uso de un identificador de clave
+para poder especificar la clave deseada.
+En el siguiente ejemplo Javier actualiza su clave pública con nuevas firmas
+desde el servidor de claves <parameter>certserver.pgp.com</parameter> y acto
+seguido envía su copia de la clave pública de Arancha al mismo servidor de
+claves para que se actualice con las claves que él mismo pueda haber
+añadido.
+
+<screen width="80">
+<prompt>javier:~$</prompt> <userinput>gpg --keyserver certserver.pgp.com
+--recv-key D58711B7</userinput>
+gpg: requesting key D58711B7 from certserver.pgp.com ...
+gpg: key D58711B7: 1 new signature
+
+gpg: Total number processed: 1
+gpg: new signatures: 1
+<prompt>javier:~$</prompt> <userinput>gpg --keyserver certserver.pgp.com
+--send-key arancha at nav.es</userinput>
+gpg: success sending to 'certserver.pgp.com' (status=200)
+</screen>
+
+Existen varios servidores de claves en funcionamiento en todo el mundo.
+Los servidores más importantes están sincronizados de modo que es posible
+elegir un servidor de claves cercano a nosotros en Internet y usarlo de
+forma regular para enviar y recibir claves.
+</para>
+</sect1>
+
+</chapter>
+
Added: gnupg-doc/trunk/gph/ru/Makefile.am
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/gph/ru/Makefile.am?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/gph/ru/Makefile.am (added)
+++ gnupg-doc/trunk/gph/ru/Makefile.am Fri May 8 09:00:27 2009
@@ -1,0 +1,18 @@
+
+EXTRA_DIST = manual.sgml c1.sgml c2.sgml c3.sgml c4.sgml c5.sgml c6.sgml \
+ c7.sgml license.sgml signatures.jpg
+
+
+pkgdata_DATA = manual.dvi manual.ps manual.html manual.texi
+
+BUILT_SOURCES = manual.dvi manual.texi
+
+manual.dvi : signatures.eps
+
+
+signatures.eps : signatures.jpg
+ convert $< $@
+
+
+include $(top_srcdir)/common/rules.am
+
Added: gnupg-doc/trunk/mini_howto/de/Makefile
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/mini_howto/de/Makefile?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/mini_howto/de/Makefile (added)
+++ gnupg-doc/trunk/mini_howto/de/Makefile Fri May 8 09:00:27 2009
@@ -1,0 +1,19 @@
+all: ps dvi html txt rtf
+
+rtf:
+ sgml2rtf --language=de --charset=latin GPGMiniHowto.sgml
+
+dvi:
+ sgml2latex --language=de --charset=latin --output=dvi GPGMiniHowto.sgml
+
+GPGMiniHowto.ps \
+ps:
+ sgml2latex --language=de --charset=latin --output=ps GPGMiniHowto.sgml
+
+GPGMiniHowto.html \
+html:
+ sgml2html --language=de --charset=latin GPGMiniHowto.sgml
+
+GPGMiniHowto.txt \
+txt:
+ sgml2txt --language=de --charset=latin GPGMiniHowto.sgml
Added: gnupg-doc/trunk/mini_howto/en/GPGMiniHowto.sgml
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/mini_howto/en/GPGMiniHowto.sgml?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/mini_howto/en/GPGMiniHowto.sgml (added)
+++ gnupg-doc/trunk/mini_howto/en/GPGMiniHowto.sgml Fri May 8 09:00:27 2009
@@ -1,0 +1,725 @@
+<!doctype linuxdoc system>
+<article>
+
+<title>Gnu Privacy Guard (GnuPG) Mini Howto (English)
+
+<author>Brenno J.S.A.A.F. de Winter (English)
+<tt><brenno at dewinter.com></tt>
+
+Michael Fischer v. Mollard (German)
+<tt><fischer at math.uni-goettingen.de></tt>
+
+Arjen Baart
+<tt><arjen at andromeda.nl></tt>
+
+<date>Version 0.1.3 May 17, 2002
+
+<abstract>
+ This documents explains how to use the GNU Privacy
+ Guard (GnuPG), an Open Source OpenPGP compatible encryption system
+ To keep this program totally free the use of the RSA algorithm and
+ other patented algorithm has been avoided. The document was originally
+ written by Michael Fischer v. Mollar in German. The text has been
+ translated and adjusted on some points and cannot be considered as a
+ full one-on-one copy.
+</abstract>
+
+<toc>
+
+<sect>Concepts<label id="GPG-Minihowto-Concept">
+<p>
+<#if output=latex2e>
+<em><bf>Remark for printed versions:</bf> Due to technical difficulties the
+ double hyphen, which indicates the long options of GnuPG, in text
+ embedded in paragraphs are represented individually as single hyphens. So
+ please read double hyphens with long options.
+ </em>
+</#if>
+</p>
+
+<sect1>Public Key Encryption
+<p>
+
+Classic methods for encryption only use one key for encryption. The sender
+encrypts the message with this key. To be able to decrypt this the receiver
+needs to have this very same key. This key must have been given to the
+receiver in a way, that others won't have had the opportunity to obtain this
+key. If somebody else does have the key, this method of encryption is useless.
+
+<p>
+The use of so-called Public Keys can solve this problem. Public Keys is a
+concept where two keys are involved. One key is a Public Key that can be
+spread through all sorts of media and may be obtained by anyone. The other
+key is the Private Key. This key is secret and cannot be spread. This key is
+only available to the owner. When the system is well implemented the secret
+key cannot be derived from the public key. Now the sender will crypt the
+message with the public key belonging to the receiver.
+Then decryption will be done with the secret key of the
+receiver.
+
+<p>
+Crucial in this concept is that the secret key remains a secret and should
+not be given away or become available to anyone else but the owner of this
+key. YOU CANNOT SEND THIS KEY OVER THE INTERNET. Also it is very unwise to
+use GnuPG over <tt>telnet</tt> (you might consider never to use telnet based
+on the high security risks).
+
+<sect1>Digital Signatures
+<p>
+
+In order to prove that a message was really sent by the alleged sender the
+concept of Digital Signatures was invented. As the name says a message is
+digitally signed by the sender. By using this signature you can check the
+authenticity of a message. Using this will reduce the risk for Trojan horses
+(a message that claims to be a patch to a certain problem but actually contains
+a virus or does something bad with data on your computer). Also information or
+data can be verified as coming from a legitimate source and thus be regarded
+as real.
+
+<p>
+A digital signature is made through a combination of the secret key and the
+text. Using the senders public key the message can be verified. Not only will
+be checked if the correct sender is involved, also the content will be checked.
+So you know that the message comes from the sender and has not been changed
+during the transportation process.
+
+<sect1>Web of trust
+<p>
+A weak point of the Public key algorithms is the spreading of the public keys.
+A user could bring a public key with false user ID in circulation. If with
+this particular key messages are made, the intruder can decode and read the
+messages. If the intruder passes it on then still with a genuine public key coded to the
+actual recipient, this attack is not noticeable.
+
+<p>
+The PGP solution (and because of that automatically the GnuPG solution)
+exists in signing codes. A public key can be signed by other people. This
+signature acknowledges that the key used by the UID (User Identification)
+actually belongs to the person it claims to be. It is then up to the user of
+GnuPG how far the trust in the signature goes. You can consider a key as
+trustworthy when you trust the sender of the key and you know for sure that
+the key really belongs to that person. Only when you can trust the key of the
+signer, you can trust the signature. To be absolutely positive that the key is
+correct you have to compare the finger print over reliable channels before
+giving absolute trust.
+
+<sect1>Boundaries to security
+<p>
+
+If you have data that you would like to remain confidential, there is more to
+it than just determining which encoding algorithm to use. You should be thinking
+about your system security in general. Basically we consider PGP to be secure
+and as I write this documents no incidents of PGP being cracked are known to me.
+But that doesn't mean that all encoding must be safe then (for instance the NSA
+wouldn't notify me if they cracked PGP somehow, neither would other people who
+crack for real malicious grounds). But even if the PGP is fully 'unhackable',
+other means can be used to attack the security. Early February 1999 a Trojan Horse had
+been found that searched for secret PGP keys on the hard disk and FTP-ed them
+away. If the password has been chosen badly the secret key can easily be
+cracked.
+
+<p>
+Another technical possibility (although more difficult) is a Trojan Horse that
+broadcasts keyboard entries. Also possible (but very difficult) is to pass
+the content of a screen along. Then no cracking of scrambled messages needs to
+be done. For all these risks there need to be a good, well-thought security plan
+that is actually deployed.
+
+<p>
+It is not a goal to create paranoia among people, but to point out that a lot
+needs to be done to be more secure. The most important thing is to realize that
+encryption is just one step to security and is not a total solution. Trojan
+horses as they appeared in the Melissa virus in March 1999 proved that many
+companies are not prepared for that.
+
+<sect>Installation
+<p>
+<sect1>Sources for GnuPG.
+<p>
+
+The official download site is:
+<url url="http://www.gnupg.org/download.html" name="GnuPG Homepage">.
+At that location you will find links to mirror sites.
+
+Due to legal restrictions it is not allowed to download GnuPG from servers
+based in the USA. The USA imposes export restrictions on the export of
+cryptographic software. This is why PGP is always available in an international
+and a national (for the USA) version.
+For the international version the source code has been exported in a printed format
+as a book. In Europe (Oslo) it has
+been scanned. More information on that can be found on
+<url url="http://www.pgpi.com" name="International PGP Homepage">.
+The international version of PGP is
+free to be imported into the United States as long as it is not re-exported again.
+
+<p>
+If you already have an installed version of GnuPG or PGP, you should check the
+signature of the file (see <ref id="GPG-Minihowto-signatures" name="Signatures">).
+
+<sect1>Configuration
+<p>
+You can obtain GnuPG as a Debian Package, as a RPM package (Redhat Package Manager)
+or in source code.
+GnuPG is included in the latest RedHat Linux distributions.
+To check if you have GnuPG installed on your system, use:
+
+<tscreen><verb>rpm -q gnupg</verb></tscreen>
+
+The packages are installed as binary files with the
+tools needed for Linux platforms. When you need GnuPG for different platforms
+you need to compile this yourself. It would be appreciated when you make
+alternative installation methods for different platforms available to the
+general public.
+<p>
+
+Since development for the major part takes place with Linux (x86), translation to
+different systems should not be regarded as being a problem. The actual list of
+known operating systems that support GnuPG can be found on
+ <htmlurl url="http://www.gnupg.org" name="GnuPG Homepage">.
+The procedure as described below is pretty platform independent. This procedure can
+be used to install GnuPG out of a source code tar-ball.
+
+<p>
+
+Unpack the tar-ball with the command:
+<tscreen><verb>tar xvzf gnupg-?.?.?.tar.gz</verb></tscreen>
+
+After the unpack, please step into the directory containing the source code.
+Then type
+
+<tscreen><verb>./configure</verb></tscreen>
+
+When doing this nothing special should happen. With
+
+<tscreen><verb>./configure --help</verb></tscreen>
+
+you can view the available configuration settings for compilation. If problems
+occur that have to do with internationalization (GET text), you can include
+a version that is delivered with the source code by using the option
+<tt>--with-included-gettext</tt> or switch it of by using
+the <tt>--disable-NLS</tt> option.
+
+<sect1>Compile
+<p>
+
+After this we want to compile the stuff by typing:
+<tscreen><verb>make</verb></tscreen>
+This should work without any problems. If any problems occur take the following
+steps (in the same order as described here): First try to solve this yourself
+(of course also by using the available documentation).
+Then make sure that your problem is not a known bug (check the BUGS file on http://www.gnupg.org).
+Then ask someone you know. If
+these steps do not solve your problem post a question to the GnuPG-mailing list
+(see <ref id="GPG-Minihowto-Informationsources" name="Informationsources">). If
+the problem is path related, you should try <tt>make clean</tt>, then run
+<tt>configure</tt> again and retry to compile. If that doesn't work it is
+time to panic.
+
+<sect1>Installation
+<p>
+
+Now type:
+<tscreen><verb>make install</verb></tscreen>
+to actually copy the program and the man-pages into the installation directory.
+If you didn't change the installation directory when you did ./configure the
+<tt>usr/local/share/gnupg/</tt> will be the installation directory. You can
+find this directory in the file <tt>options.skel</tt>. When you change this
+<tt>options.skel</tt>. If you copy this to <tt>~/.gnupg/options</tt> the
+appropriate adjustments will be used as standard. Copying should occur
+automatically when creating <tt>~/.gnupg/</tt>. All possible options are
+well documented and explaining them here would not be useful.
+
+<p>
+You can run GnuPG as suid root. So the program runs with all the rights the
+superuser has. By doing this you exclude the possibility that certain parts
+of the program are stored externally and then could be read by anyone. It is
+not feasible for me to judge on the value of this risk. But running the program
+as suid root one should be alert to the danger of Trojan horses. Since a Trojan
+horse running as superuser can damage an entire system. If for this reason (or
+any other reason) you choose not run GnuPG as root you can switch off the warning
+by setting
+<tt>no-secmem-warning</tt> in <tt>~/.gnupg/options</tt>.
+
+
+<sect>Using keys<label id="GPG-Minihowto-Key">
+<p>
+<sect1>Creating a key
+<p>
+
+With
+<tscreen><verb>gpg --gen-key</verb></tscreen>
+a new key-pair is created (key pair: secret and public key).
+The first question is which algorithm can be used. You can read more about algorithms in
+<url url="http://www.hertreg.ac.uk/ss/pgpfaq.html" name="PGP DH
+vs. RSA FAQ"> or in <ref id="BSchneier" name="Applied Cryptography">.
+You can easily (and maybe you should - since it is used so
+widely) use DSA/ ElGamal. This is not patented.
+
+<p>
+The next question is key length. This is something that is very user dependent.
+You need to choose between security and calculating time.
+If a key is longer the risk for cracking the message when intercepted decreases.
+But with a larger key calculation time also increases.
+If computing time is an issue you still should consider that you want to
+use the key for sometime.
+We all know that arithmetic performance increases very quickly,
+since new processors are getting quicker and quicker.
+So keep this in mind. The minimal key length GnuPG demands is 768 bits.
+However some people say you should have at a key-size of 2048 bits
+(which is also really a maximum with GnuPG at this moment).
+For DSA 1024 is a standard size. When security is a top priority and
+performance is less an issue you ought to pick the largest key-size available.
+
+<p>
+The system now asks to enter names, comment and e-mail address. Based upon the
+entries here the code is calculated. You can change these settings later. See
+<ref id="GPG-Minihowto-KPAdministration" name="Administering keypairs">.
+
+<p>
+Finally you have to enter a password (actually passphrase would be more
+appropriate, since blanks are allowed). This password is used to be able to use
+the functionality which belongs to your secret key. A good passphrase contains
+the following elements:
+<itemize>
+ <item>it is long,
+ <item>it has special (non alphanumeric) characters,
+ <item>it is something special (not a name),
+ <item>it is very hard to guess (so NOT names, birth dates, phone numbers,
+ number of a credit card/checking account, names and number of children, ...)
+</itemize>
+By sometimes using CaPItaLs aNd SOMEtimes NoT you can build in further security.
+When you make your password make sure that you WILL NOT FORGET it.
+Since if you do messages are not legible and the use of your secret key has gone.
+It might
+be wise to generate some kind of a certificate containing this information
+(of course be careful that nobody gets to your passphrase). See
+<ref id="GPG-Minihowto-Revoke" name="Revoke">.
+
+<p>
+After everything was entered the systems starts generating the keys.
+This will take some time.
+During that time it needs to collect a lot of random data.
+By working in a different screen you can help the system collecting
+changing random data. As you understand by now, the key will be always different.
+If you generate a key now and 5 minutes later with exactly the same data,
+you'll get two different keys. Now you must understand why you shouldn't
+forget your password.
+
+
+<sect1>Exporting keys
+<p>
+
+The command for exporting a key for a user is:
+<tscreen><verb>gpg --export [UID]</verb></tscreen>
+If no UID has been submitted all present keys will be exported. By default the
+output is set to <tt>stdout</tt>. But with the <tt>-o</tt> option this is
+sent to a file. It may be advisable using the option <tt>-a</tt> to write the
+key to a 7-bit ASCII file instead of a binary file.
+
+<p>
+By exporting public keys you can broaden your horizon. Others can start
+contacting you securely. This can be done by publishing it on your homepage, by
+finger, through a key server like http://www.pca.dfn.de/dfnpca/pgpkserv/
+or any other method you can think of.
+
+<sect1>Importing keys
+<p>
+
+When you received someone's public key (or several public keys)
+you have to add them to your key database in order to be able to use them.
+To import into the
+database the command looks like this:
+<tscreen><verb>gpg --import [Filename]</verb></tscreen>
+if the filename is omitted the data will be read from
+<tt>stdin</tt>.
+
+<sect1>Revoke a key<label id="GPG-Minihowto-Revoke">
+<p>
+For several reasons you may want to revoke an existing key. For instance:
+the secret key has been stolen or became available to the wrong people,
+the UID has been changed, the key is not large enough anymore, etc.
+In all these cases the command to revoke the key is:
+<tscreen><verb>gpg --gen-revoke</verb></tscreen>
+This creates a revocation certificate.
+<em>To be able to do this, you need a secret key
+</em>, else anyone could revoke your certificate. This has one disadvantage.
+If I do not know the passphrase the key has become useless.
+But I cannot revoke the key! To overcome this problem it is wise to create a
+revoke license when you create a key pair. And if you do so, keep it safe!
+This can be on disk, paper, etc.
+Make sure that this certificate will not fall into wrong hands!!!!
+If you don't someone else can issue the revoke certificate for your
+key and make it useless.
+
+<sect1>Key administration<label id="GPG-Minihowto-KPAdministration">
+<p>
+
+With the GnuPG system comes a file that acts as some kind of database. In this file
+all data regarding keys with the information that comes with the keys is stored
+(everything until the Ownertrust values: for more information on that read
+<ref id="GPG-Minihowto-KSigning" name="Key signing">).
+With
+<tscreen><verb>gpg --list-keys</verb></tscreen>
+all present keys will be displayed. To see the signatures as well type:
+<tscreen><verb> gpg --list-sigs </verb></tscreen>
+(see <ref
+id="GPG-Minihowto-KSigning" name="Key signing"> for further information).
+To see the fingerprints type:
+<tscreen><verb>gpg --fingerprint </verb></tscreen>
+You want to see "Fingerprints" to ensure that somebody is really
+the person they claim (like in a telephone call). This command will result in
+a list of relatively small numbers.
+
+To list the secret keys you type:
+<tscreen><verb>gpg --list-secret-keys</verb></tscreen>
+Note that listing fingerprints and signatures from private keys has no use whatsoever.
+<p>
+In order to delete a public key you type:
+<tscreen><verb>gpg --delete-key UID </verb></tscreen>
+For deleting a secrete key you type:
+<tscreen><verb> gpg --delete-secret-key </verb></tscreen>
+<p>
+There is one more important command that is relevant for working with keys.
+<tscreen><verb>gpg --edit-key UID</verb></tscreen>
+Using this you can edit (among other things) the expiration date, add a
+fingerprint and sign your key. Although it is too logic to mention. For this
+you need your passphrase. When entering this you will see a command line.
+
+<sect1>Key signing<label id="GPG-Minihowto-KSigning">
+<p>
+
+As mentioned before in the introduction there is one major Achilles' heel
+in the system. This is the authenticity of public keys.
+If you have a wrong public key
+you can say bye bye to the value of your encryption.
+To overcome such risks there is a possibility of signing keys.
+In that case you place your signature over the key,
+so that you are absolutely positive that this key is valid.
+This leads to the situation where the
+signature acknowledges that the user ID mentioned in the key is
+actually the owner of that key. With that reassurance you can start encrypting.
+
+<p>
+Using the <tt>gpg --edit-key UID</tt> command for the key that needs to be
+signed you can sign it with the <tt>sign</tt> command.
+
+<p>
+<em>You should only sign a key as being authentic when you are ABSOLUTELY SURE
+that the key is really authentic!!!</em>.
+So if you are positive you got the key yourself (like on a key signing party)
+or you got the key through other means and checked it (for instance by phone)
+using the fingerprint-mechanism. You should never sign a key based on any assumption.
+
+<p>
+Based on the available signatures and
+"ownertrusts"
+GnuPG determines the validity of keys. Ownertrust is a value that the owner of
+a key uses to determine the level of trust for a certain key. The values are
+<itemize>
+ <item> 1 = Don't know
+ <item> 2 = I do NOT trust
+ <item> 3 = I trust marginally
+ <item> 4 = I trust fully
+</itemize>
+If the user does not trust a signature it can say so and thus disregard the
+signature. Trust information is not stored in the same file as the keys,
+but in a separate file.
+
+<sect>Encrypt and decrypt<label id="GPG-Minihowto-encrypt">
+
+<p>
+After installing everything and configuring everything in the way we want,
+we can start on encrypting and decrypting.
+<p>
+When encrypting or decrypting it is possible to have more than one private key
+in use. If this occurs you need to select the active key. This can be done by
+using the option <tt>-u UID</tt> or by using the option <tt> --local-user UID</tt>.
+This causes the default key to use to be replaced by wanted key.
+<p>
+If you want to change recipient this can be done by the option <tt>-r</tt>
+or by the option <tt>--recipient</tt>.
+
+<sect1>Encrypt
+<p>
+
+The command to encrypt is
+<tscreen><verb>gpg -e Recipient [Data]</verb></tscreen>
+or
+<tscreen><verb>gpg --encrypt Recipient [Data]</verb></tscreen>
+To avoid the risk that somebody else claims to be you,
+it is very useful to sign everything you encrypt, see
+<ref id="GPG-Minihowto-signatures" name="signatures">.
+
+<sect1>Decrypt
+<p>The command for decrypting is:
+<tscreen><verb>gpg [-d] [Data] </verb></tscreen>
+or
+<tscreen><verb>gpg [--decrypt] [Data]</verb></tscreen>
+Also here <tt>stdout</tt> is preset, but with the <tt>-o</tt> option you can
+redirect the output to a file.
+
+<sect>Signing and checking signatures<label id="GPG-Minihowto-signatures">
+<p>
+
+To sign data with your own key, use the command:
+<tscreen><verb>gpg -s (or --sign) [Data]</verb></tscreen>
+By doing this also compression takes place. This means that the result is not
+legible. If you want a legible result you can use:
+
+<tscreen><verb>gpg --clearsign [Data]</verb></tscreen>
+this will make sure that the results are clearly legible. Furthermore it does
+the same (signing data).
+
+With
+<tscreen><verb>gpg -b (or --detach-sign) [Data]</verb></tscreen>
+you can write the signature in a separate file. It is highly recommended to use
+this option especially when signing binary files (like archives for instance).
+Also the <tt>--armor</tt> option can be extremely useful here.
+
+<p>
+Quite often you find that data is encrypted and signed as well. The full
+instruction looks like:
+<tscreen><verb>gpg [-u Sender] [-r Recipient] [--armor] --sign --encrypt [Data]
+</verb></tscreen>
+
+The functionality of the options <tt>-u</tt> (<tt>--local-user</tt>) and <tt>-r</tt>
+(<tt>--recipient</tt>) are as described before.
+
+<P>
+When encrypted data has been signed as well, the signature is checked when the
+data is decrypted. You can check the signature of signed data by using the command:
+<tscreen><verb>gpg [--verify] [Data]</verb></tscreen>
+This will only work (of course) when you own the public key of the sender.
+
+<sect>Front ends<label id="GPG-Minihowto-frontends">
+<p>
+
+To make life a lot easier in using GnuPG, you have a wide choice of programs
+that either use or support GnuPG encryption.
+There are graphical front ends that put your key administration at the
+click of a mouse button and many MUAs (Mail User Agents) let you encrypt and
+sign your Email messages seamlessly.
+A nearly full list of front ends is available from the
+<htmlurl url="http://www.gnupg.org/frontends.html" name="GnuPG Frontends"> page.
+We will highlight a few of them in this section.
+
+<sect1>Graphical interfaces
+<p>
+
+<sect2>GPA
+<p>
+<htmlurl url="http://www.gnupg.org/gpa.html" name="GPA">, the <em>GNU Privacy
+Assistant</em> is a graphical user interface for the GNU Privacy Guard (GnuPG).
+This is the standard graphical front end, provided by the GnuPG project.
+With GPA, you can view your keyring, import and export keys, generate keys,
+edit key properties and encrypt, sign or decrypt documents.
+Installing GPA is easy.
+Download the tarball, unpack and do the usual
+<tscreen><verb>./configure; make; make install.</verb></tscreen>
+Start the program by typing
+<tscreen><verb>gpa</verb></tscreen>
+
+<sect2>Seahorse
+<p>
+<htmlurl url="http://seahorse.sourceforge.net/" name="Seahorse">
+is a GNOME front-end for GnuPG.
+It can be used for sign, encrypt, verify and decrypt text and files.
+The text can be taken from the clipboard, or written directly in the little
+editor it has. Seahorse is also a key manager, which can be used to edit
+almost all the properties of the keys stored in your key rings.
+You can install Seahorse from a Debian package (RPMs are not available
+at this time) or from the source tarball.
+Installing from source is like any other package. Download, untar, configure
+and make install.
+The installation puts seahorse in <tt>/usr/local</tt> and puts a menu item in
+the Gnome 'Applications' menu.
+
+<sect2>Geheimnis
+<p>
+
+<htmlurl url="http://geheimnis.sourceforge.net/" name="Geheimnis"> is a
+front end for GnuPG which is based upon KDE.
+It is supposed to have all the functions from GPA or Seahorse.
+However, when I tried to make the program, I got stuck on a missing
+library (/usr/lib/libfam.la).
+
+<sect1>Email programs
+<p>
+Most popular Email programs (or MUAs) support GnuPG. Among these are
+at least the following:
+<itemize>
+ <item>Mozilla
+ <item>Pine
+ <item>Kmail
+ <item>Eudora
+ <item>Mutt
+ <item>exmh
+</itemize>
+
+There are probably more; it is hardly possible to try them all.
+
+<p>
+Using GnuPG support in your mail program lets you decrypt Email messages sent
+to you that are encrypted with your public key, sign your messages so the
+receiving party can make sure you are the author and encrypt your Email
+with the public keys of your recipients.
+
+<sect2>Mozilla and Enigmail
+<p>
+Mozilla does not have GnuPG support in itself. To use GnuPG encryption with
+Mozilla, you must install a plug-in, such as
+<htmlurl url="http://enigmail.mozdev.org/" name="EnigMail">.
+Enigmail is a "plugin" for Mozilla/Netscape Mail which allows users to access
+the authentication and encryption features provided by the popular
+GPG and PGP software.
+Enigmail can encrypt/sign mail when sending, and also decrypt/authenticate
+received mail. It can also import/export public keys.
+
+<p>
+Installing EnigMail on a RedHat Linux system is especially easy, since RPMs
+for the latest Mozilla release are available.
+There are two packages to install: <tt>mozilla-enigmail-0.39-3.i386.rpm</tt>
+and <tt>mozilla-ipc-0.99-0_rh7x.rpm</tt>.
+After installing these RPMs, restart Mozilla (or Netscape 6.x) and you should be
+able to use GnuPG in your Email.
+Note, however, that EnigMail encrypts only the text of your message.
+Attachments are not encrypted by EnigMail; you'll have encrypt any files
+you want to attach separately.
+On other systems, you probably have to install EnigMail from source code.
+
+<sect2>Kmail
+<p>
+Kmail, the standard Email program for KDE has integrated support for GnuPG
+and PGP encryption.
+To set things up so you can sign and decrypt messages, you have to enter your
+GnuPG user ID in the 'Identity' section of the Kmail configuration.
+When you send a new message, the message will not be signed or encrypted by
+default. You have to check the 'Sign message' and 'Encrypt message' buttons
+in the tool bar.
+
+<sect>Sources of information<label id="GPG-Minihowto-Informationsources">
+<p>
+
+<sect1>GnuPG
+<p>
+
+<itemize>
+ <item>The <url url="http://www.gnupg.org" name="GnuPG Homepage">
+
+ <item>The GnuPG Mailing list, including archives and descriptions on the
+ <htmlurl url="http://www.gnupg.org/docs.html" name="GnuPG Homepage">.
+
+ <item>The information enclosed in the GnuPG project (updated until version 0.9.2),
+ however not yet very extensively done. And not to forget:
+ <tscreen><verb>gpg --help </verb></tscreen>. This is very valuable information.
+
+
+</itemize>
+
+<sect1>PGP
+<p>
+PGP is the older and (still) widely spread and used cryptography program.
+Through the years a lot of documents have been made.
+This can be considered as very useful information.
+A lot of that information is so general that you can apply that to GnuPG as well.
+Check out the following URLs for these documents:
+
+<itemize>
+ <item>The <url url="http://www.pgpi.com" name="International PGP Homepage">
+ <item>The <url url="http://www.hertreg.ac.uk/ss/pgpfaq.html"
+ name="PGP DH vs. RSA FAQ"> has information on the differences of these two
+ algorithms. These are the two algorithms used by GnuPG.
+</itemize>
+
+<sect1>Keyservers
+<p>
+<itemize>
+ <item> <url url="http://www.keyserver.net" name="Keyserver.net">
+ <item> <url url="http://wwwkeys.eu.pgp.net">
+</itemize>
+
+<sect1>Books
+<p>
+
+<itemize>
+ <item>B. Schneier, "Applied Cryptography, Second
+ Edition", Wiley, 1996 <label id="BSchneier"> Deutsche Ausgabe
+ unter dem Titel "Angewandte Kryptographie", Addison-Wesley, 1996
+</itemize>
+
+
+<sect>About this document
+<p>
+Copyright © 1999 Brenno J.S.A.A.F. de Winter (English version)
+Copyright © 1999 Michael Fischer v. Mollard (original German version)
+Copyright © 2002 Arjen Baart (Dutch version)
+<p>
+ This document is free documentation you can redistribute it and/or
+ modify it under the terms of the GNU Library General Public
+ License as published by the Free Software Foundation; either
+ version 2 of the License, or (at your option) any later version.
+
+ This library is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Library General Public License for more details.
+<p>
+ You should have received a copy of the GNU Library General Public
+ License along with this library; if not, write to the
+ Free Software Foundation, Inc., 59 Temple Place - Suite 330,
+ Boston, MA 02111-1307, USA.
+
+<sect1>Versions
+<p>
+Original German versions:
+Version 0.1 was the first version in German
+<p>
+<bf>Version 0.1.0 (English) April 30th 1999, Dutch Queen's Day.</bf>
+<itemize>
+<item>
+ This version is the translation of the German version in English with some
+ adjustments.
+</itemize>
+
+<p>
+<bf>Version 0.1.1 (German)</bf>
+<p>
+<itemize>
+ <item>New section "Boundaries to security"
+ <item>Improved explanation of signatures
+ <item>Changes after comments from Werner Koch (thanks!)
+</itemize>
+
+<p>
+<bf>Version 0.1.2 (English) April 3, 2002</bf>
+<itemize>
+ <item>Corrected a few typos.
+ <item>New section about front ends.
+</itemize>
+
+</itemize>
+
+<p>
+<bf>Version 0.1.3 (Dutch) May 17, 2002</bf>
+<itemize>
+ <item>This version is a translation of the English version into Dutch.
+</itemize>
+
+All changes are documented in a diff file:
+<url url="http://www.stud.uni-goettingen.de/~s070674/GnuPGMiniHowto/" name="dieses Dokument">
+<p>
+For the English or Dutch version:
+All remarks for this document can be sent to Brenno J.S.A.A.F. de Winter
+(<tt><htmlurl url="mailto:brenno at dewinter.com" name="brenno at dewinter.com"></tt>).
+or Arjen Baart
+(<tt><htmlurl url="mailto:arjen at andromeda.nl" name="arjen at andromeda.nl"></tt>).
+Comments help us make a better document and are greatly appreciated.
+
+For the German version:
+Anregungen, Kritik, Verbesserungen und Erweiterungen
+einfach an Michael Fischer v. Mollard (<tt><htmlurl
+url="mailto:fischer at math.uni-goettingen.de"
+name="fischer at math.uni-goettingen.de"></tt>) senden, damit dieses
+Dokument weiter verbessert werden kann.
+
+</article>
Added: gnupg-doc/trunk/mini_howto/en/Makefile
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/mini_howto/en/Makefile?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/mini_howto/en/Makefile (added)
+++ gnupg-doc/trunk/mini_howto/en/Makefile Fri May 8 09:00:27 2009
@@ -1,0 +1,35 @@
+#
+# $Id: Makefile,v 1.1 2003/02/26 23:30:03 lolo Exp $
+#
+# Translation by:
+# 2003 Josep Monés i Teixidor <jmones at puntbarra.com>
+#
+
+LINUXDOC := linuxdoc
+
+all: GPGMiniHowto_big.html \
+ GPGMiniHowto.html \
+ GPGMiniHowto.txt \
+ GPGMiniHowto.rtf \
+ GPGMiniHowto.dvi \
+ GPGMiniHowto.pdf \
+ GPGMiniHowto.ps
+
+
+# One HTML big file
+GPGMiniHowto_big.html : GPGMiniHowto.sgml
+ $(LINUXDOC) -B html -s 0 $<
+ mv GPGMiniHowto.html $@
+
+# Other formats
+GPGMiniHowto.html \
+GPGMiniHowto.txt \
+GPGMiniHowto.rtf :\
+GPGMiniHowto.% : GPGMiniHowto.sgml
+ linuxdoc -B $* $<
+
+GPGMiniHowto.dvi \
+GPGMiniHowto.pdf \
+GPGMiniHowto.ps :\
+GPGMiniHowto.% : GPGMiniHowto.sgml
+ linuxdoc -B latex -o $* $<
Added: gnupg-doc/trunk/mini_howto/es/Makefile
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/mini_howto/es/Makefile?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/mini_howto/es/Makefile (added)
+++ gnupg-doc/trunk/mini_howto/es/Makefile Fri May 8 09:00:27 2009
@@ -1,0 +1,35 @@
+#
+# $Id: Makefile,v 1.1 2003/02/26 23:30:03 lolo Exp $
+#
+# Translation by:
+# 2003 Josep Monés i Teixidor <jmones at puntbarra.com>
+#
+
+LINUXDOC := linuxdoc
+
+all: gpgminicomo_big.html \
+ gpgminicomo.html \
+ gpgminicomo.txt \
+ gpgminicomo.rtf \
+ gpgminicomo.dvi \
+ gpgminicomo.pdf \
+ gpgminicomo.ps
+
+
+# One HTML big file
+gpgminicomo_big.html : gpgminicomo.sgml
+ $(LINUXDOC) -B html -s 0 $<
+ mv gpgminicomo.html $@
+
+# Other formats
+gpgminicomo.html \
+gpgminicomo.txt \
+gpgminicomo.rtf :\
+gpgminicomo.% : gpgminicomo.sgml
+ linuxdoc -B $* $<
+
+gpgminicomo.dvi \
+gpgminicomo.pdf \
+gpgminicomo.ps :\
+gpgminicomo.% : gpgminicomo.sgml
+ linuxdoc -B latex -o $* $<
Added: gnupg-doc/trunk/mini_howto/nl/Makefile
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/mini_howto/nl/Makefile?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/mini_howto/nl/Makefile (added)
+++ gnupg-doc/trunk/mini_howto/nl/Makefile Fri May 8 09:00:27 2009
@@ -1,0 +1,35 @@
+#
+# $Id: Makefile,v 1.1 2003/02/26 23:30:03 lolo Exp $
+#
+# Translation by:
+# 2003 Josep Monés i Teixidor <jmones at puntbarra.com>
+#
+
+LINUXDOC := linuxdoc
+
+all: GPGMiniHowto_big.html \
+ GPGMiniHowto.html \
+ GPGMiniHowto.txt \
+ GPGMiniHowto.rtf \
+ GPGMiniHowto.dvi \
+ GPGMiniHowto.pdf \
+ GPGMiniHowto.ps
+
+
+# One HTML big file
+GPGMiniHowto_big.html : GPGMiniHowto.sgml
+ $(LINUXDOC) -B html -s 0 $<
+ mv GPGMiniHowto.html $@
+
+# Other formats
+GPGMiniHowto.html \
+GPGMiniHowto.txt \
+GPGMiniHowto.rtf :\
+GPGMiniHowto.% : GPGMiniHowto.sgml
+ linuxdoc -B $* $<
+
+GPGMiniHowto.dvi \
+GPGMiniHowto.pdf \
+GPGMiniHowto.ps :\
+GPGMiniHowto.% : GPGMiniHowto.sgml
+ linuxdoc -B latex -o $* $<
Added: gnupg-doc/trunk/pgp2x/en/Makefile
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/pgp2x/en/Makefile?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/pgp2x/en/Makefile (added)
+++ gnupg-doc/trunk/pgp2x/en/Makefile Fri May 8 09:00:27 2009
@@ -1,0 +1,19 @@
+debian-all: pgp2x.html pgp2x.ps pgp2x.txt
+
+pgp2x.html: pgp2x.sgml
+ sgmltools --backend=onehtml pgp2x.sgml >> build.log 2>&1
+ touch pgp2x.html
+
+pgp2x.ps: pgp2x.sgml
+ sgmltools --backend=ps pgp2x.sgml >> build.log 2>&1
+
+pgp2x.txt: pgp2x.sgml
+ sgmltools --backend=txt pgp2x.sgml >> build.log 2>&1
+
+install: debian-all
+ install -m 0644 pgp2x.ps $(DESTDIR)/
+ install -m 0644 pgp2x.txt $(DESTDIR)/
+ install -m 0644 pgp2x.html $(DESTDIR)/
+
+clean:
+ rm -rf *.dvi *.aux *.pdf *.html *.tex *.log *.eps *.gz *.jpg *.ps *.txt build.log *~ pgp2x
Added: gnupg-doc/trunk/pgp2x/es/Makefile
URL: http://svn.debian.org/wsvn/pkg-gnupg/gnupg-doc/trunk/pgp2x/es/Makefile?rev=97&op=file
==============================================================================
--- gnupg-doc/trunk/pgp2x/es/Makefile (added)
+++ gnupg-doc/trunk/pgp2x/es/Makefile Fri May 8 09:00:27 2009
@@ -1,0 +1,19 @@
+debian-all: pgp2x.html pgp2x.ps pgp2x.txt
+
+pgp2x.html: pgp2x.sgml
+ sgmltools --backend=onehtml pgp2x.sgml >> build.log 2>&1
+ touch pgp2x.html
+
+pgp2x.ps: pgp2x.sgml
+ sgmltools --backend=ps pgp2x.sgml >> build.log 2>&1
+
+pgp2x.txt: pgp2x.sgml
+ sgmltools --backend=txt pgp2x.sgml >> build.log 2>&1
+
+install: debian-all
+ install -m 0644 pgp2x.ps $(DESTDIR)/
+ install -m 0644 pgp2x.txt $(DESTDIR)/
+ install -m 0644 pgp2x.html $(DESTDIR)/
+
+clean:
+ rm -rf *.dvi *.aux *.pdf *.html *.tex *.log *.eps *.gz *.jpg *.ps *.txt build.log *~ pgp2x
More information about the Pkg-gnupg-commit
mailing list