19 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | oldsite/
2 | stage/
3 | scratch/
4 | /web/sitemap.org
5 | .*.orgx
6 | /web/theindex.inc
7 | /web/faq/gnupg-faq.pdf
8 | /web/faq/gnupg-faq.tex
9 | /web/faq/gnupg-faq.txt
10 | /web/swdb.lst
11 | /web/swdb.lst.sig
12 | /misc/blog.gnupg.org/index.html
13 | /misc/blog.gnupg.org/20*.html
14 | /misc/blog.gnupg.org/headlines.txt
15 | /misc/id/eddsa-for-openpgp/draft.txt
16 | *~
17 | .DS_Store
18 | ._.DS_Store
19 | default.profraw
20 | /misc/id/openpgp-webkey-service/draft.xml
21 | /misc/id/common/reference.RFC.8615.xml
22 | /misc/id/openpgp-webkey-service/.refcache/
23 |
--------------------------------------------------------------------------------
/misc/jenkins/bin/gnupg-w32.patch:
--------------------------------------------------------------------------------
1 | diff --git a/autogen.rc b/autogen.rc
2 | index 36948178f..4aa1993d8 100644
3 | --- a/autogen.rc
4 | +++ b/autogen.rc
5 | @@ -15,13 +15,6 @@ esac
6 | case "$myhost" in
7 | w32)
8 | configure_opts="
9 | - --with-gpg-error-prefix=@SYSROOT@
10 | - --with-ksba-prefix=@SYSROOT@
11 | - --with-libgcrypt-prefix=@SYSROOT@
12 | - --with-libassuan-prefix=@SYSROOT@
13 | - --with-zlib=@SYSROOT@
14 | - --with-regex=@SYSROOT@
15 | - --with-npth-prefix=@SYSROOT@
16 | --disable-g13
17 | "
18 | ;;
19 |
--------------------------------------------------------------------------------
/web/share/campaign/img/vidmenu.svg:
--------------------------------------------------------------------------------
1 |
14 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.3394.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | Advanced Encryption Standard (AES) Key Wrap Algorithm
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
--------------------------------------------------------------------------------
/web/misc/donations.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - Donations
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 |
5 | * Donations
6 |
7 | Maintaining and improving GnuPG is costly. For more than 10 years
8 | now, g10^code, a German company owned and headed by GnuPG's
9 | principal author Werner Koch, is bearing the majority of these
10 | costs. To help them carry on this work, they need your support.
11 |
12 | The donation page used to be hosted over at the g10^code GmbH site.
13 | Since May 2014 the donation page is a proper part of this site:
14 |
15 | - [[../donate/index.org][New donation page]]
16 |
--------------------------------------------------------------------------------
/web/documentation/faqs.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - FAQ
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 |
5 | * GnuPG Frequently Asked Questions
6 |
7 | The GnuPG FAQ is available in 2 formats:
8 |
9 | - [[https://www.gnupg.org/faq/gnupg-faq.html][HTML]]
10 | - [[https://www.gnupg.org/faq/gnupg-faq.txt][Plain text]]
11 |
12 | The FAQ is generated using this [[https://git.gnupg.org/cgi-bin/gitweb.cgi?p%3Dgnupg-doc.git%3Ba%3Dblob_plain%3Bf%3Dweb/faq/gnupg-faq.org][source code]]. If you are looking for
13 | the old and outdated FAQ, please go to [[https://www.gnupg.org/ftp/gcrypt/gnupg/GnuPG-FAQ.old.txt][here]].
14 |
15 | # eof
16 |
--------------------------------------------------------------------------------
/misc/blog.gnupg.org/index.org:
--------------------------------------------------------------------------------
1 | # Index of all blog entries
2 | #+STARTUP: showall
3 |
4 | #+HTML:
The GnuPG blog
5 |
6 | #+HTML:
7 | #+HTML:
8 |
9 | * List of all blog entries
10 | :PROPERTIES:
11 | :CUSTOM_ID: blogindex
12 | :END:
13 |
14 | #+HTML:
15 | #+HTML:
16 |
17 | * Comments
18 |
19 | We do not provide a feature to comment on a blog. Instead please
20 | send remarks to the gnupg-users mailing list using the blog title
21 | for the subject line. This helps to keep the discussion at one
22 | place and not to spread it over different media.
23 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.2822.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | Internet Message Format
7 |
8 |
9 |
10 |
11 | This document specifies a syntax for text messages that are sent between computer users, within the framework of "electronic mail" messages. [STANDARDS-TRACK]
12 |
13 |
14 |
15 |
16 |
--------------------------------------------------------------------------------
/web/legal.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - Legal Issues
2 | #+STARTUP: showall
3 | #+SETUPFILE: "share/setup.inc"
4 |
5 | * Legal Issues
6 |
7 | Some countries have regulations on the use of cryptographics systems; it
8 | may be unlawful to use GnuPG in these countries.
9 |
10 | For a guide to International Laws regarding cryptography, please see
11 | Bert-Jaap Koops' [[http://www.cryptolaw.org][Crypto Law Survey]] .
12 | # Note that there is no valid https server for cryptolaw.org
13 |
14 | Note that in January 2000, the US Department of Commerce relaxed the
15 | rules about [[http://www.crypto.com/exports/][exporting]] cryptography, in particular for free software
16 | projects.
17 |
--------------------------------------------------------------------------------
/web/software/pinentry/index.org:
--------------------------------------------------------------------------------
1 | #+STARTUP: showall
2 | #+SETUPFILE: "../../share/setup.inc"
3 |
4 | * pinentry
5 |
6 | /pinentry/ is a small collection of dialog programs that allow GnuPG
7 | to read passphrases and PIN numbers in a secure manner. There are
8 | versions for the common GTK and Qt toolkits as well as for the text
9 | terminal (Curses).
10 |
11 | See the [[../../download/index.org::pinentry][download]] section for the latest tarball.
12 |
13 | The development takes place in a Git repo:
14 | #+BEGIN_EXAMPLE
15 | git clone git://git.gnupg.org/pinentry.git
16 | #+END_EXAMPLE
17 | For more information see our [[../../download/git.org][Git page]].
18 |
--------------------------------------------------------------------------------
/web/software/gpa/screenshots.org:
--------------------------------------------------------------------------------
1 | #+STARTUP: showall
2 | #+SETUPFILE: "../../share/setup.inc"
3 |
4 |
5 | * GPA - Screenshots
6 |
7 | This page shows you a collection of screenshots of GPA, the Gnu
8 | Privacy Assistant.
9 |
10 | ** Main Window
11 |
12 | Files are managed for de/encryption. Access to all keyring
13 | management functionalities are available via the menu. The most
14 | usual commands are available via the toolbar.
15 |
16 | [[file:screenshots/main_window.png]]
17 |
18 | ** Public keyring dialog
19 |
20 | The personal collection of public keys (keyring) can be browsed and
21 | managed.
22 |
23 | [[file:screenshots/public_keyring_dialog.png]]
24 |
--------------------------------------------------------------------------------
/web/donate/donate-thanks.ja.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - 寄付 - ありがとう
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 |
5 | * 寄付 - ありがとう
6 |
7 | *GnuPGのわたしたちの仕事に対して寄付してくださり、大変ありがとうございます。*
8 |
9 | [[https://www.gnupg.org/donate/kudos.html][寄付者一覧]]は30分おきに更新されます。
10 | あなたの名前が掲載されるまでしばらくお待ちください。名前を指定していない場合は掲載されません。
11 |
12 | こちらがあなたの寄付の詳細です:
13 | #+BEGIN_HTML
14 |
27 | #+END_HTML
28 |
--------------------------------------------------------------------------------
/web/misc/index.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - Miscellaneous
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 |
5 | * Archive
6 |
7 | This is a list of pages we used in the past. The content is
8 | not anymore relevant for the project but we keep them here in case
9 | people like to dive into old times.
10 |
11 | - [[file:thanks.org][Thanks]] - We have to thank many people for making GnuPG possible.
12 | - [[file:links.org][Links]] - Cryptography is a wide-spread science and other people
13 | have something to tell about.
14 | - [[file:logo-contest.org][Logo Contest]] - GnuPG needs a new Logo.
15 | - [[file:../legal.org][Law survey]] - Info on the legal issues of using cryptography.
16 |
--------------------------------------------------------------------------------
/web/faq/Makefile:
--------------------------------------------------------------------------------
1 |
2 | srcdir = .
3 |
4 | # Note that you need a recent version of emacs23 with org-mode 7.01h
5 | #
6 | # Note that due to a problem with hyperref we are currently not able
7 | # to build a pdf version
8 | #
9 | # --visit "$(srcdir)/gnupg-faq.org" \
10 | # --eval "(org-latex-export-to-pdf)"\
11 | #
12 |
13 | gnupg-faq.txt gnupg-faq.html: gnupg-faq.org
14 | @set -e; \
15 | emacs --batch \
16 | --eval "(require 'org)" \
17 | --visit "$(srcdir)/gnupg-faq.org" \
18 | --eval "(org-ascii-export-to-ascii)"
19 |
20 | faq-online: gnupg-faq.txt gnupg-faq.html
21 | set -e; \
22 | user=werner ; \
23 | echo "Uploading current FAQ to ftp.gnupg.org ..."; \
24 | scp gnupg-faq.txt $${user}@ftp.gnupg.org:gcrypt/gnupg/GnuPG-FAQ.txt; \
25 | echo "...ready"
26 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.5785.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Defining Well-Known Uniform Resource Identifiers (URIs)
6 |
7 |
8 |
9 | This memo defines a path prefix for "well-known locations", "/.well-known/", in selected Uniform Resource Identifier (URI) schemes. [STANDARDS-TRACK]
10 |
11 |
12 |
13 |
14 |
--------------------------------------------------------------------------------
/web/documentation/sites.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - Other web sites and cards
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 |
5 | * Press review
6 |
7 | [[file:pressreview.org][Articles on GnuPG]]
8 |
9 | * Other web sites
10 |
11 | This page shows a list of web sites which are somehow related to GnuPG.
12 |
13 | - [[http://pgp.iijlab.net/][Japanese PGP page]] :: A site in Japanese dedicated to PGP.
14 | - [[http://pt.gnupg.org.][Portuguese GnuPG site]] :: A site in Portuguese dedicated to GnuPG.
15 | - [[http://pgpru.com/][Russian OpenPGP site]] :: A site in Russian with a forum dedicated to
16 | OpenPGP.
17 |
18 | * OpenPGP card implementations
19 |
20 | OpenPGP cards can be purchased from:
21 |
22 | - [[https://www.floss-shop.de/en/security-privacy/][FLOSS-Shop]] (formerly kernelconcepts)
23 |
--------------------------------------------------------------------------------
/misc/jenkins/bin/gnupg-2.0-w32.patch:
--------------------------------------------------------------------------------
1 | diff --git a/autogen.sh b/autogen.sh
2 | index 605babfa9..1a9654f0d 100755
3 | --- a/autogen.sh
4 | +++ b/autogen.sh
5 | @@ -87,15 +87,7 @@ if test "$1" = "--build-w32"; then
6 | $tsdir/configure --enable-maintainer-mode --prefix=${w32root} \
7 | --host=${host} --build=${build} \
8 | --enable-gpgtar \
9 | - --with-gpg-error-prefix=${w32root} \
10 | - --with-ksba-prefix=${w32root} \
11 | - --with-libgcrypt-prefix=${w32root} \
12 | - --with-libassuan-prefix=${w32root} \
13 | - --with-zlib=${w32root} \
14 | - --with-regex=${w32root} \
15 | - --with-pth-prefix=${w32root} \
16 | - --with-libiconv-prefix=${w32root} \
17 | - --with-adns=${w32root} "$@"
18 | + "$@"
19 | rc=$?
20 | exit $rc
21 | fi
22 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.2782.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | A DNS RR for specifying the location of services (DNS SRV)
6 |
7 |
8 |
9 |
10 | This document describes a DNS RR which specifies the location of the server(s) for a specific protocol and domain. [STANDARDS-TRACK]
11 |
12 |
13 |
14 |
15 |
--------------------------------------------------------------------------------
/web/software/npth/index.org:
--------------------------------------------------------------------------------
1 | #+STARTUP: showall
2 | #+SETUPFILE: "../../share/setup.inc"
3 |
4 | * The New GNU Portable Threads Library
5 |
6 | /nPth/ is a library to provide the GNU Pth API and thus a
7 | non-preemptive threads implementation.
8 |
9 | In contrast to GNU Pth is is based on the system's standard threads
10 | implementation. This allows the use of libraries which are not
11 | compatible to GNU Pth. Experience with a Windows Pth emulation
12 | showed that this is a solid way to provide a co-routine based
13 | framework.
14 |
15 | See the [[../../download/index.org::npth][download]] section for the latest tarball.
16 |
17 | The development takes place in a Git repo:
18 | #+BEGIN_EXAMPLE
19 | git clone git://git.gnupg.org/npth.git
20 | #+END_EXAMPLE
21 | For more information see our [[../../download/git.org][Git page]].
22 |
--------------------------------------------------------------------------------
/web/donate/donate-thanks.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - Donate - Thank you
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 |
5 | * Donate - Thank you
6 |
7 | *Thank you very much for your donation to our work on GnuPG.*
8 |
9 | Note that the [[https://www.gnupg.org/donate/kudos.html][list of donors]] is updated every 30 minutes, thus
10 | have some patience until you see your name. If you did not give a
11 | name you won’t be listed at all.
12 |
13 | Here are the details of your donation:
14 | #+BEGIN_HTML
15 |
16 |
17 |
18 | #+END_HTML
19 |
20 | Your credit card statement should list this donation as /GnuPG
21 | donation/. If you have any questions please contact /donations/ at
22 | /gnupg.org/.
23 |
24 |
25 | #+BEGIN_HTML
26 |
29 | #+END_HTML
30 |
--------------------------------------------------------------------------------
/misc/howtos.gnupg.org/card-howto/en/ChangeLog:
--------------------------------------------------------------------------------
1 | 2006-06-29 Werner Koch
2 |
3 | Finally fixed utf-8 problems again.
4 |
5 | 2006-06-29 Werner Koch
6 |
7 | Updated from card-howto module. Added Athena-ASEDRIVE picture.
8 |
9 | 2006-02-07 Werner Koch
10 |
11 | Updated from card-howto module. Added KAAN and CM4040 pictures.
12 |
13 | 2005-10-30 Werner Koch
14 |
15 | Updated from card-howto module. Added SCR335 picture.
16 |
17 | 2005-10-30 Werner Koch
18 |
19 | Updated from card-howto module.
20 |
21 | 2005-09-26 Werner Koch
22 |
23 | Updated from card-howto module.
24 |
25 | 2005-05-12 Werner Koch
26 |
27 | Updated from card-howto module.
28 |
29 | 2005-04-30 Werner Koch
30 |
31 | Copied first versions from the card-howto module.
32 |
33 |
34 |
--------------------------------------------------------------------------------
/misc/id/common/reference.I-D.josefsson-eddsa-ed25519.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | EdDSA and Ed25519
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 | The elliptic curve signature scheme EdDSA and one instance of it called Ed25519 is described. An example implementation and test vectors are provided.
18 |
19 |
20 |
21 |
22 |
24 |
25 |
--------------------------------------------------------------------------------
/misc/id/rfc4880bis/abstract.mkd:
--------------------------------------------------------------------------------
1 | { Work in progress to update OpenPGP }
2 |
3 | This document is maintained in order to publish all necessary
4 | information needed to develop interoperable applications based on the
5 | OpenPGP format. It is not a step-by-step cookbook for writing an
6 | application. It describes only the format and methods needed to read,
7 | check, generate, and write conforming packets crossing any network.
8 | It does not deal with storage and implementation questions. It does,
9 | however, discuss implementation issues necessary to avoid security
10 | flaws.
11 |
12 | OpenPGP software uses a combination of strong public-key and symmetric
13 | cryptography to provide security services for electronic
14 | communications and data storage. These services include
15 | confidentiality, key management, authentication, and digital
16 | signatures. This document specifies the message formats used in
17 | OpenPGP.
18 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.6637.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | Elliptic Curve Cryptography (ECC) in OpenPGP
7 |
8 |
9 |
10 |
11 | This document defines an Elliptic Curve Cryptography extension to the OpenPGP public key format and specifies three Elliptic Curves that enjoy broad support by other standards, including standards published by the US National Institute of Standards and Technology. The document specifies the conventions for interoperability between compliant OpenPGP implementations that make use of this extension and these Elliptic Curves. [STANDARDS-TRACK]
12 |
13 |
14 |
15 |
16 |
--------------------------------------------------------------------------------
/web/donate/donate-thanks.de.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - Donate - Danke schön
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 |
5 | * Spende - Danke schön
6 |
7 | *Vielen Dank für Ihre Spende zur Unterstützung unserer Arbeit an GnuPG.*
8 |
9 | Bitte beachten Sie, daß die [[https://www.gnupg.org/donate/kudos.html][Liste der Spender]] etwa alle 15 Minuten
10 | aktualisiert wird. Es kann deswegen einige Zeit dauern, bis Ihre Spende
11 | und, sofern gewünscht, Ihr Name dort erscheint.
12 |
13 | Hier ist eine Zusammenfassung Ihrer Spende:
14 | #+BEGIN_HTML
15 |
16 |
17 |
18 | #+END_HTML
19 |
20 | Auf Ihrer Kreditkartenabrechnung wird diese Spende als /GnuPG
21 | donation/ erscheinen. Falls Sie Fragen haben, so schreiben Sie
22 | bitte an /donations/ at /gnupg.org/.
23 |
24 |
25 | #+BEGIN_HTML
26 |
29 | #+END_HTML
30 |
--------------------------------------------------------------------------------
/web/donate/donate-thanks.fr.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - Faire un don - Merci
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 |
5 | * Donation - Merci !
6 |
7 | *Merci beaucoup pour votre don à notre travail sur GnuPG.*
8 |
9 | Notez que la [[https://www.gnupg.org/donate/kudos.html][liste des donateurs]]
10 | n'est mise à jour que toutes les 30 minutes, et donc votre nom n'y est peut-être
11 | pas encore affiché. Si vous n'avez pas entré de nom dans le formulaire, alors
12 | vous ne serez pas listé·e.
13 |
14 | Voici les détails de votre donation:
15 | #+BEGIN_HTML
16 |
17 |
18 |
19 | #+END_HTML
20 |
21 | Votre reçu bancaire devrait lister cette transaction sous l'intitulé /GnuPG
22 | donation/. En cas de question, veuillez contacter /donations/ at
23 | /gnupg.org/.
24 |
25 |
26 | #+BEGIN_HTML
27 |
30 | #+END_HTML
31 |
--------------------------------------------------------------------------------
/web/documentation/manuals.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - Manuals
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 |
5 | * Manuals
6 |
7 | This is a list of online available manuals. Those marked as "draft" may
8 | document features not yet available in the released software version.
9 |
10 | - GnuPG manual :: [[file:manuals/gnupg/][HTML]], [[file:manuals/gnupg.pdf][PDF]]
11 | - Libgcrypt manual :: [[file:manuals/gcrypt/][HTML]], [[file:manuals/gcrypt.pdf][PDF]].
12 | - Libksba manual :: [[file:manuals/ksba/][HTML]], [[file:manuals/ksba.pdf][PDF]].
13 | - Libassuan manual :: [[file:manuals/assuan/][HTML]], [[file:manuals/assuan.pdf][PDF]].
14 | - GPGME manual :: [[file:manuals/gpgme/][HTML]], [[file:manuals/gpgme.pdf][PDF]].
15 | - Scute manual :: [[file:manuals/scute/][HTML]], [[file:manuals/scute.pdf][PDF]].
16 |
17 | Man pages extracted from the above documents are installed with the
18 | software but are also available online [[file:manpage.org][online man page]].
19 |
--------------------------------------------------------------------------------
/web/share/setup.inc:
--------------------------------------------------------------------------------
1 | # Setup file for this site.
2 | #
3 | # Note: To include swdb.org in an org file add the line
4 | # #+GPGWEB-NEED-SWDB
5 | # in the first 2k of the file. It is not possible to include that file
6 | # from here because we don't have a way to specify gpgweb-root-dir as
7 | # part of the filename. A dedicated pre-process feature like above is
8 | # probably more efficient anyway.
9 |
10 |
11 | # Org version 8 does not anymore expand macros in all places. We use
12 | # some ugly macros instead of the #+begin_example et al.
13 |
14 | #+macro: begin_example @@html:
@@
15 | #+macro: end_example @@html:
@@
16 | #+macro: begin_chksum @@html:
@@
17 | #+macro: end_chksum @@html:
@@
18 |
19 | #+macro: twodashes @@html:--@@
20 |
21 | # Org rendering of links with an included '=' is broken. Thus we use
22 | # a macro here.
23 | #+macro: CVE [[https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-$1][CVE-$1]]
24 |
25 | # eof
26 |
--------------------------------------------------------------------------------
/misc/id/common/reference.I-D.irtf-cfrg-eddsa.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Edwards-curve Digital Signature Algorithm (EdDSA)
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 | The elliptic curve signature scheme Edwards-curve Digital Signature Algorithm (EdDSA) is described. The algorithm is instantiated with recommended parameters for the Curve25519 and Curve448 curves. An example implementation and test vectors are provided.
18 |
19 |
20 |
21 |
22 |
24 |
25 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.0822.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
6 |
7 |
8 | This document revises the specifications in RFC 733, in order to serve the needs of the larger and more complex ARPA Internet. Some of RFC 733's features failed to gain adequate acceptance. In order to simplify the standard and the software that follows it, these features have been removed. A different addressing scheme is used, to handle the case of internetwork mail; and the concept of re-transmission has been introduced. Obsoletes RFC 733, NIC 41952.
9 |
10 |
11 |
12 |
13 |
14 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.3156.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | MIME Security with OpenPGP
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 | This document describes how the OpenPGP Message Format can be used to provide privacy and authentication using the Multipurpose Internet Mail Extensions (MIME) security content types described in RFC 1847. [STANDARDS-TRACK]
18 |
19 |
20 |
21 |
22 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.3713.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | A Description of the Camellia Encryption Algorithm
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 | This document describes the Camellia encryption algorithm. Camellia is a block cipher with 128-bit block size and 128-, 192-, and 256-bit keys. The algorithm description is presented together with key scheduling part and data randomizing part. This memo provides information for the Internet community.
16 |
17 |
18 |
19 |
20 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.7748.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Elliptic Curves for Security
6 |
7 |
8 |
9 |
10 | This memo specifies two elliptic curves over prime fields that offer a high level of practical security in cryptographic applications, including Transport Layer Security (TLS). These curves are intended to operate at the ~128-bit and ~224-bit security level, respectively, and are generated deterministically based on a list of required properties.
11 |
12 |
13 |
14 |
15 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.3447.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1
7 |
8 |
9 |
10 |
11 |
12 |
13 | This memo represents a republication of PKCS #1 v2.1 from RSA Laboratories' Public-Key Cryptography Standards (PKCS) series, and change control is retained within the PKCS process. The body of this document is taken directly from the PKCS #1 v2.1 document, with certain corrections made during the publication process. This memo provides information for the Internet community.
14 |
15 |
16 |
17 |
18 |
--------------------------------------------------------------------------------
/misc/blog.gnupg.org/20131030-new-blog-first-post.org:
--------------------------------------------------------------------------------
1 | # Old blog post converted from HTML to ORG.
2 | #+AUTHOR: Sam Tuke
3 | #+DATE: 30th October 2013
4 |
5 | ** New blog, first post
6 |
7 | Welcome to Gnu Privacy Guard's new blog! We're planning some major
8 | changes to gnupg.org and how the project communicates in general. I'm
9 | Sam, and I'll be writing updates here as our work progresses. In
10 | future this blog will be replaced with a more beautiful and featureful
11 | alternative, but bear with us as we get from here to there.
12 |
13 | For more timely updates you can follow our Twitter accounts:
14 | [[https://twitter.com/intent/follow?screen_name=GnuPrivacyGuard][@GnuPrivacyGuard]] and [[https://twitter.com/intent/follow?screen_name=gnupg][@GnuPG]]. That's right, we have two! But I'm going
15 | to combine them shortly so it's easier to keep track *[UPDATE:
16 | accounts now merged! Stick with @GnuPG]*.
17 |
18 | For more information, see our [[http://gnupg.totemapp.com/company][press contact page]] hosted on
19 | Totem. That's all for now.
20 |
--------------------------------------------------------------------------------
/misc/howtos.gnupg.org/card-howto/en/gnupg-ccid:
--------------------------------------------------------------------------------
1 | #!/bin/bash
2 | #
3 | # taken from libgphoto2
4 | #
5 | # Sets up newly plugged in card reader so that only members of the
6 | # group can access it
7 |
8 | GROUP=scard
9 |
10 | # can access it from user space. (Replace scard with the name of the
11 | # group you want to have access to the card reader.)
12 | #
13 | # Note that for this script to work, you'll need all of the following:
14 | # a) a line in the file /etc/hotplug/gnupg-ccid.usermap that corresponds
15 | # to the card reader you are using.
16 | # b) a group "scard" where all users allowed access to the
17 | # card reader are listed
18 | # c) a Linux kernel supporting hotplug and usbdevfs
19 | # d) the hotplug package (http://linux-hotplug.sourceforge.net/)
20 | #
21 | # In the usermap file, the first field "usb module" should be named
22 | # "gnupg-ccid" like this script.
23 | #
24 |
25 | if [ "${ACTION}" = "add" ] && [ -f "${DEVICE}" ]
26 | then
27 | chmod o-rwx "${DEVICE}"
28 | chgrp "${GROUP}" "${DEVICE}"
29 | chmod g+rw "${DEVICE}"
30 | fi
31 |
--------------------------------------------------------------------------------
/web/verein/token.org:
--------------------------------------------------------------------------------
1 | #+TITLE: The membership token
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 |
5 | * The Membership Token
6 |
7 | *This is currently under development*
8 |
9 | Member of the Verein may receive a dedicated crypto token to secure
10 | their communication. The token will implement the OpenPGP card
11 | specification and we will make the membership number a part of the
12 | token's serial number.
13 |
14 | Obviously the hardware and the software will be under a free license.
15 | We will use the Gnuk token from our founding member Niibe-san.
16 |
17 | - Website :: http://www.gniibe.org/FST-01/fst-01.html
18 | - Hardware :: git://git.gniibe.org/gnuk/fst-01.git
19 | - Firmware :: git://git.gniibe.org/gnuk/gnuk.git
20 |
21 | The license for the schematics is /Creative Commons Attribution 3.0
22 | Unported License (CC BY 3.0)/. The license for the PCB is /Creative
23 | Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0)/. The
24 | license for the Firmare is the /GNU General Public Licence version 3
25 | or later (GPLv3+)/.
26 |
--------------------------------------------------------------------------------
/misc/vcards/data.sample:
--------------------------------------------------------------------------------
1 | # Data for use with vcard-template.tex
2 |
3 |
4 | Type: gpg
5 | Name: Werner Koch
6 | Title:
7 | Mail:
8 | Jabber:
9 | Ptype: m
10 | Phone:
11 | Fpr: 8061 5870 F5BA D690 3336 86D0 F2AD 85AC 1E42 B367
12 |
13 | Type: g10
14 | Name: Werner Koch
15 | Title:
16 | Mail:
17 | Jabber:
18 | Ptype: p
19 | Phone:
20 | Fpr: 8061 5870 F5BA D690 3336 86D0 F2AD 85AC 1E42 B367
21 |
22 | Type: gpg
23 | Name: David Shaw
24 | Mail:
25 | Fpr: 7D92 FD31 3AB6 F373 4CC5 9CA1 DB69 8D71 9924 2560
26 |
27 | Type: gpg
28 | Name: Niibe Yutaka
29 | Mail:
30 | Fpr: 1241 24BD 3B48 62AF 7A0A 42F1 00B4 5EBD 4CA7 BABE
31 |
32 | Type: gpg
33 | Name: Jussi Kivilinna
34 | Mail:
35 | Fpr: 60C7 E68E 6964 603F B163 6E47 068B FB23 A931 6686
36 |
37 | Type: gpg
38 | Name: Neal H. Walfield
39 | Mail:
40 | Fpr: 8F17 7771 18A3 3DDA 9BA4 8E62 AACB 3243 6300 52D9
41 |
42 | Type: gpg
43 | Name: Kai Michaelis
44 | Mail:
45 | Fpr:
46 |
47 | Type: gpg
48 | Name: Justus Winter
49 | Mail:
50 | Fpr:
51 |
52 | Type: gpg
53 | Name: Andre Heinecke
54 | Mail:
55 | Fpr:
56 |
57 |
58 | # eof
59 |
--------------------------------------------------------------------------------
/web/software/tools.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - Tools
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 | #+OPTIONS: ^:{}
5 |
6 | * Tools
7 |
8 | Here is a list of GnuPG related tools:
9 |
10 | If you feel wanting to improve this list, please, fill in a [[#gpgweb][Problem
11 | Report]] form.
12 |
13 | - [[file:swlist.org::#enigform][enigform]] :: Mozilla Firefox extension for HTTP+OpenPGP support.
14 | - [[file:swlist.org::#keylookup][Keylookup]] :: Is a tool to fetch keys from keyservers.
15 | - [[file:swlist.org::#macgpg][MacGPG]] :: Mac-related GnuPG tools
16 | - [[file:swlist.org::#mod-auth-openpgp][mod_auth_openpgp]] :: Apache module for HTTP+OpenPGP support
17 | - [[file:swlist.org::#pgpdump-web][PGPdump Web interface]] :: Can be used to analyze OpenPGP data
18 | formats.
19 | - [[file:swlist.org::#pinentry][Pinentry]] :: Secure PinEntry Dialog.
20 | - [[https://bitbucket.org/skskeyserver/sks-keyserver/overview][SKS]] :: Popular keyserver software.
21 | - [[https://hockeypuck.github.io/][Hockeypuck]] :: Keyserver written in Go.
22 |
--------------------------------------------------------------------------------
/web/donate/kudos-2014.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - List of Donors - 2014
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 |
5 | * People who donated money to GnuPG in 2014
6 |
7 | #+HTML:
8 | #+HTML:
9 | #+HTML:
[please reload in a few minutes while the list is being updated]
10 | #+HTML:
11 | #+HTML:
12 |
13 | Thank you.
14 |
15 | * Participants of the crowdfunding campaign
16 |
17 | On December 19, 2013 we launched a crowdfunding campaign at the
18 | [[Goteo.org]] site to raise money for a updating the GnuPG
19 | infrastructure and help releasing version 2.1. Our goal of 24000
20 | Euro was reached within 27 hours and in the weeks following the
21 | gross donations reached 36000 Euro. Here is the list of
22 | participants who opted for being listed:
23 |
24 | #+HTML:
25 | #+HTML:
26 | #+HTML:
[please reload in a few minutes while the list is being updated]
27 | #+HTML:
28 | #+HTML:
29 |
30 | Thank you.
31 |
--------------------------------------------------------------------------------
/misc/blog.gnupg.org/20140127-find-fosdem.org:
--------------------------------------------------------------------------------
1 | # Old blog post converted from HTML to ORG.
2 | #+STARTUP: showall
3 | #+AUTHOR: Sam Tuke
4 | #+DATE: 27th January 2014
5 |
6 | ** Find us at FOSDEM
7 |
8 | #+CAPTION: Keysigning at FOSDEM
9 | [[file:img/keysigning-party-s.jpg]]
10 |
11 | On Friday Werner and Sam are heading to [[https://fosdem.org/2014/][FOSDEM]], the largest Free
12 | Software conference in Europe, along with many GnuPG hackers, users,
13 | and supporters. [[http://gnupg.totemapp.com/company][Get in touch]] if you'd like to talk about the existing
14 | or future campaigns while we're there.
15 |
16 | There won't be a GnuPG booth this year but, we shall be busy with
17 | meetings and mingling. Notes and contacts for us can be left at the
18 | [[https://fosdem.org/2014/stands/][FSFE booth]].
19 |
20 | And don't forget that you're invited to the continent's biggest
21 | keysigning party, organised by FOSDEM volunteers. Today is the last
22 | opportunity to [[https://fosdem.org/2014/keysigning/][submit your key]], which is necessary for
23 | participation. Get to it!.
24 |
25 | Bring your ideas. See you there.
26 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.3629.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | UTF-8, a transformation format of ISO 10646
7 |
8 |
9 |
10 |
11 | ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8, the object of this memo. UTF-8 has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo obsoletes and replaces RFC 2279.
12 |
13 |
14 |
15 |
16 |
17 |
--------------------------------------------------------------------------------
/web/imprint.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - Imprint
2 | #+STARTUP: showall
3 | #+SETUPFILE: "share/setup.inc"
4 |
5 | * Imprint
6 |
7 | GnuPG is an international community project run by volunteers and
8 | not a legal entity. g10^code GmbH is the privately owned legal
9 | entity behind the GnuPG project. They employ all paid developers
10 | and re-invest the majority their profits into the development of
11 | GnuPG and related free software. See also this [[https://www.gnupg.org/blog/20141214-gnupg-and-g10.html][article]].
12 |
13 | g10 Code GmbH\\
14 | Bergstr. 3a\\
15 | D-40699 Erkrath\\
16 | Germany
17 |
18 | g10 Code GmbH is registered at Amtsgericht
19 | Wuppertal under HRB 14459.\\
20 | Geschäftsführung: Werner Koch.\\
21 | VAT-Id: DE215605608.\\
22 | Phone: +49-2104-173855\\
23 | Mail: info@g10code.com
24 |
25 | Note that we provide the phone number and mail address only for
26 | legal reasons. Please do not call g10^code to ask for free support.
27 | For paid support see their [[https://g10code.com/contact.html][contact page]].
28 |
29 | Please see [[file:privacy-policy.org][here]] for the privacy policy.
30 |
--------------------------------------------------------------------------------
/misc/howtos.gnupg.org/vn/info-english.htm:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 | Info English
8 |
9 |
10 |
11 |
12 |
This document was translation of English version into Vietnam by me.
13 |
14 | Was translation from Version 0.1.1 (English)
15 |
16 | I'm Vietnamese. I'm Linux User. I'm using Mandrake and Debian Linux on my PC.
17 | You can contact with me:
18 |
19 | My public key:
20 |
21 | http://www.polarhome.com/~binhnx/contact/binhnx2000.asc
22 |
23 | Nguyen Xuan Binh (binhnx2000@yahoo.com)
24 |
25 | http://binhnx.hypermart.net/ (My Site)
26 | http://www.vieteam.com/ (VTF Forum)
27 | http://www.sfod.org/ (SFOD Forum)
28 | http://www.polarhome.com/~vicki (My Group)
29 |
30 | Note: I can speak English and German. But not good ;-)
31 |
32 |
33 |
34 |
35 |
36 |
--------------------------------------------------------------------------------
/web/software/ntbtls/index.org:
--------------------------------------------------------------------------------
1 | #+STARTUP: showall
2 | #+SETUPFILE: "../../share/setup.inc"
3 |
4 | * The Not Too Bad TLS Library
5 |
6 | /ntbTLS/ is a tiny TLS 1.2 only implementation designed to be used
7 | with Libgcrypt and LibKSBA. In particular, this library has no
8 | certificate verification code - this needs to be done by the caller.
9 | For example the GnuPG component /dirmngr/ already has code to verify
10 | certificates (for CRL and OCSP checking) and thus /ntbTLS/ is a good
11 | fit for accessing objects over the network.
12 |
13 | The code for the library is based on the TLS protocol code from
14 | PolarSSL (now known as [[https://tls.mbed.org/][mbedTLS]]) with all crypto code replaced by
15 | Libgcrypt code and all older TLS and SSL protocol support removed.
16 | The library is used by the GnuPG version of Gpg4win since 2017.
17 |
18 | See the [[../../download/index.org::ntbtls][download]] section for the latest tarball.
19 |
20 | The development takes place in a Git repo:
21 | #+BEGIN_EXAMPLE
22 | git clone git://git.gnupg.org/ntbtls.git
23 | #+END_EXAMPLE
24 | For more information see our [[../../download/git.org][Git page]].
25 |
--------------------------------------------------------------------------------
/web/verein/members.org:
--------------------------------------------------------------------------------
1 | #+TITLE: Members of the GnuPG e.V
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 |
5 | * List of GnuPG e.V Members.
6 |
7 | To apply for membership please write to board at gnupg dot org. For
8 | regular members we expect that you have a more than average interest
9 | in GnuPG and that you are active in development or in evangelizing
10 | end-to-end encryption. It is also possible to support the Verein by
11 | applying as a supporting member. See the membership regulations
12 | ([[https://gnupg.org/ftp/verein/beitragsordnung.en.pdf][English]], [[https://gnupg.org/ftp/verein/beitragsordnung.de.pdf][German]]) for details.
13 |
14 |
15 | ** The regular members
16 |
17 | - Andre Heinecke
18 | - Bernhard Reiter
19 | - Damien Goutte-Gattat
20 | - Daniel Kahn Gillmor
21 | - Guilhem Moulin
22 | - Holger Smolinski
23 | - Justus Winter
24 | - Kai Michaelis
25 | - Kristian Fiskerstrand
26 | - Martin Gollowitzer
27 | - Maurice Kemmann
28 | - Neal Walfied
29 | - Phil Pennock
30 | - Werner Koch
31 | - Yutaka Niibe
32 |
33 | *** Former members
34 |
35 | - Marcus Brinkmann
36 |
37 | ** The supporting members
38 |
39 | /none so far/
40 |
--------------------------------------------------------------------------------
/web/software/libksba/index.org:
--------------------------------------------------------------------------------
1 | #+STARTUP: showall
2 | #+SETUPFILE: "../../share/setup.inc"
3 |
4 | * Libksba
5 |
6 | /Libksba/ is a library to make the tasks of working with X.509
7 | certificates, CMS data and related objects more easy. It provides a
8 | highlevel interface to the implemented protocols and presents the
9 | data in a consistent way. There is no more need to worry about all
10 | the nasty details of the protocols. The API gives the C programmer
11 | an easy way of interacting with the data. It copes with the version
12 | details X.509 protocols tend to have as well as with the many
13 | different versions and dialects. Applications must usually cope with
14 | all of this and it has to be coded over and over again. /Libksba/
15 | hides this by providing just one API which does the Right
16 | Thing\trade. Support for new features will be added as needed.
17 |
18 | See the [[../../download/index.org::libksba][download]] section for the latest tarball.
19 |
20 | The development takes place in a Git repo:
21 | #+BEGIN_EXAMPLE
22 | git clone git://git.gnupg.org/libksba.git
23 | #+END_EXAMPLE
24 | For more information see our [[../../download/git.org][Git page]].
25 |
--------------------------------------------------------------------------------
/web/verein/index.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG e.V.
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 | #+macro: atgit [[https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg-verein.git;a=blob_plain;f=$1][$2]]
5 |
6 | * The GnuPG e.V. has been dissolved
7 |
8 | The GnuPG e.V. was a charitable legal person (a German “Verein”) to
9 | improve data protection, data sovereignty and customer protection in
10 | in our supranational networked society. To achieve these goals the
11 | Verein seeks for international cooperation with people and
12 | organizations and supports the development and distribution of Free
13 | and Open Source software.
14 |
15 | The Verein was founded on February 8, 2017 by 7 active GnuPG
16 | developers. Its registration number is /VR11482/ at /Amtsgericht
17 | Düsseldorf/. The tax office Düsseldorf-Altstadt confirmed the
18 | charitable state.
19 |
20 | The membership assembly decided on 2024-08-17 to dissolve the Verein.
21 | The Amtsgericht Düsseldorf registered the termination on 2025-02-19.
22 |
23 | Creditors should check the "Amtsblatt für den Regierungsbezirk
24 | Düsseldorf, Amtsblatt Nr. 16, Öffdentlicher Anzeiger vom 17.04.2025,
25 | Ziffer 112" on how to contact the liquidator.
26 |
27 | # eof
28 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.2144.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | The CAST-128 Encryption Algorithm
7 |
8 | Entrust Technologies
9 |
10 |
11 | 750 Heron Road
12 | Ottawa
13 | Ontario
14 | K1V 1A7
15 | CA
16 | +1 613 763 9008
17 | cadams@entrust.com
18 |
19 |
20 | There is a need in the Internet community for an unencumbered encryption algorithm with a range of key sizes that can provide security for a variety of cryptographic applications and protocols.
21 | This document describes an existing algorithm that can be used to satisfy this requirement. Included are a description of the cipher and the key scheduling algorithm (Section 2), the s-boxes (Appendix A), and a set of test vectors (Appendix B).
22 |
23 |
24 |
25 |
26 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.6090.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | Fundamental Elliptic Curve Cryptography Algorithms
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 | This note describes the fundamental algorithms of Elliptic Curve Cryptography (ECC) as they were defined in some seminal references from 1994 and earlier. These descriptions may be useful for implementing the fundamental algorithms without using any of the specialized methods that were developed in following years. Only elliptic curves defined over fields of characteristic greater than three are in scope; these curves are those used in Suite B. This document is not an Internet Standards Track specification; it is published for informational purposes.
16 |
17 |
18 |
19 |
20 |
--------------------------------------------------------------------------------
/misc/id/common/reference.ED25519.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
5 |
6 |
7 | High-speed high-security signatures
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 | This paper shows that a $390 mass-market quad-core 2.4GHz
16 | Intel Westmere (Xeon E5620) CPU can create 109000 signatures per
17 | second and verify 71000 signatures per second on an elliptic curve at a
18 | 2128 security level. Public keys are 32 bytes, and signatures are 64 bytes.
19 | These performance figures include strong defenses against software side-
20 | channel attacks: there is no data flow from secret keys to array indices,
21 | and there is no data flow from secret keys to branch conditions.
22 |
23 |
24 |
25 |
27 |
28 |
--------------------------------------------------------------------------------
/web/share/campaign/img/token.svg:
--------------------------------------------------------------------------------
1 |
2 |
37 |
--------------------------------------------------------------------------------
/web/software/gpgme/index.org:
--------------------------------------------------------------------------------
1 | #+STARTUP: showall
2 | #+GPGWEB-NEED-SWDB
3 | #+SETUPFILE: "../../share/setup.inc"
4 |
5 | * GPGME
6 |
7 | /GnuPG Made Easy/ (GPGME) is a library designed to make access to
8 | GnuPG easier for applications. It provides a High-Level Crypto API
9 | for encryption, decryption, signing, signature verification and key
10 | management. Currently it uses GnuPG's OpenPGP backend as the
11 | default, but the API isn't restricted to this engine. We have, in
12 | fact, already developed a backend for CMS (S/MIME).
13 |
14 | Because the direct use of GnuPG from an application can be a
15 | complicated programming task, it is suggested that all software
16 | should try to use GPGME instead. This way bug fixes or improvements
17 | can be done at a central place and every application benefits from
18 | this. Furthermore, there is no guarentee that any particular
19 | command line option will remain exactly the same at any given point
20 |
21 | Especially authors of @@html:@@MUAs@@html:@@ should consider using GPGME.
23 |
24 | See [[../../download/index.org::#gpgme][download]] section to download the latest tarball. The manual can
25 | be read [[https://www.gnupg.org/documentation/manuals/gpgme/][here]]. The current version is {{{gpgme_ver}}}.
26 |
--------------------------------------------------------------------------------
/web/software/scute/index.org:
--------------------------------------------------------------------------------
1 | #+STARTUP: showall
2 | #+GPGWEB-NEED-SWDB
3 | #+SETUPFILE: "../../share/setup.inc"
4 |
5 | * Scute
6 |
7 | /Scute/ is a [[https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=pkcs11][PKCS#11]] provider on top of GnuPG allowing the use of
8 | GnuPG supported smartcards with [[https://www.mozilla.org/projects/security/pki/nss/][Mozilla]]'s Network Security Services
9 | and other software supporting the PKCS#11 specification.
10 |
11 | This allows you to use use those smartcards and tokens
12 | (e.g. OpenPGP card, Yubikey, TCOS) as a security device in [[https://www.mozilla.com/][Firefox]]
13 | and other software that makes use the NSS library.
14 |
15 | Supported use cases are:
16 |
17 | - [[https://en.wikipedia.org/wiki/Https][HTTPS]] client authentication with [[https://www.mozilla.com/][Firefox]]
18 | - S/MIME email signing with [[https://www.thunderbird.net][Thunderbird]]
19 | - Document signing with [[https://www.libreoffice.org/][LibreOffice]]
20 | - VPN authentication with [[https://www.openvpn.net]] (Unix only)
21 |
22 | Head to the [[../../download/index.org::#scute][download]] section to download the latest tarball. The
23 | current version is {{{scute_ver}}}. The [[https://gnupg.org/documentation/manuals/scute/][Scute Manual]] can be read
24 | on-line.
25 |
26 |
27 | #+HTML:
28 |
--------------------------------------------------------------------------------
/web/misc/gnupg-ldap-init.ldif:
--------------------------------------------------------------------------------
1 | # gnupg-ldap-init.ldif -*- conf -*-
2 | #
3 | # Entries connecting the schema specified in gnupg-ldap-schema.ldif.
4 | # Revision: 2020-10-07
5 |
6 | dn: cn=PGPServerInfo,dc=example,dc=com
7 | objectClass: pgpServerInfo
8 | cn: PGPServerInfo
9 | # Note that we suggest the use of ou=GnuPG keys instead of the often
10 | # used PGP Keys. This makes it easy to spot this is a new schema.
11 | pgpBaseKeySpaceDN: ou=GnuPG Keys,dc=example,dc=com
12 | # Using the value GnuPG here indicates that pgpVersion below has a
13 | # well-defined meaning.
14 | pgpSoftware: GnuPG
15 | # pgpVersion is a string with space delimited items:
16 | #
17 | # Item 1 - Implemented schema version. This is an integer with one
18 | # of these values:
19 | # 1 = Classic PGP schema (default)
20 | # 2 = The attributes gpgFingerprint, gpgSubFingerprint,
21 | # gpgSubCertID, and gpgMailbox are part of the schema.
22 | # Item 2 - A string with the used LDAP server
23 | # "-" = Unknown (default)
24 | # "ntds" = Windows Directory Service (AD DS)
25 | # "openldap" = OpenLDAP
26 | #
27 | pgpVersion: 2
28 |
29 | dn: ou=GnuPG Keys,dc=example,dc=com
30 | objectClass: organizationalUnit
31 | ou: GnuPG Keys
32 |
33 | dn: ou=GnuPG Users,dc=example,dc=com
34 | objectclass: organizationalUnit
35 | ou: GnuPG Users
36 |
--------------------------------------------------------------------------------
/web/software/libgpg-error/index.org:
--------------------------------------------------------------------------------
1 | #+STARTUP: showall
2 | #+SETUPFILE: "../../share/setup.inc"
3 |
4 | * Libgpg-error
5 |
6 | /Libgpg-error/ is a small library that originally defined common
7 | error values for all GnuPG components. Among these are GPG, GPGSM,
8 | GPGME, GPG-Agent, libgcrypt, Libksba, DirMngr, Pinentry, SCdaemon.
9 | Because /Libgpg-error/ is a common dependency all GnuPG components,
10 | more features have been added to the library:
11 |
12 | - An extended stream library (estream) which for example allows the
13 | use of memory or cookie based streams.
14 |
15 | - A printf implementation to provide a uniform interface on all
16 | platforms. This also includes asprintf style functions.
17 |
18 | - An implementation of locks (mutexes).
19 |
20 | - A gettext implementation for use on Windows
21 |
22 | - A Base64 decoder
23 |
24 | This library will eventually be renamed to /Libgpgrt/ to reflect
25 | that this is a runtime library for GnuPG and other software which
26 | likes to use it. The latest version already comes with a header
27 | file "gpgrt.h" which can be used instead of "gpg-error.h".
28 |
29 | See the [[file:../../download/index.org::libgpg-error][download]] section for the latest tarball.
30 |
31 | The development takes place in a Git repo:
32 | #+BEGIN_EXAMPLE
33 | git clone git://git.gnupg.org/libgpg-error.git
34 | #+END_EXAMPLE
35 | For more information see our [[../../download/git.org][Git page]].
36 |
--------------------------------------------------------------------------------
/autogen.sh:
--------------------------------------------------------------------------------
1 | #! /bin/sh
2 | # Run this to generate all the initial makefiles, etc.
3 | #
4 | # Copyright (C) 2003 g10 Code GmbH
5 | #
6 | # This file is free software; as a special exception the author gives
7 | # unlimited permission to copy and/or distribute it, with or without
8 | # modifications, as long as this notice is preserved.
9 | #
10 | # This program is distributed in the hope that it will be useful, but
11 | # WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
12 | # implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
13 |
14 | #
15 | # Check the git setup.
16 | #
17 | if [ -d .git ]; then
18 | if [ -f .git/hooks/pre-commit.sample -a ! -f .git/hooks/pre-commit ] ; then
19 | cat <&2
20 | *** Activating trailing whitespace git pre-commit hook. ***
21 | For more information see this thread:
22 | http://mail.gnome.org/archives/desktop-devel-list/2009-May/msg00084html
23 | To deactivate this pre-commit hook again move .git/hooks/pre-commit
24 | and .git/hooks/pre-commit.sample out of the way.
25 | EOF
26 | cp -av .git/hooks/pre-commit.sample .git/hooks/pre-commit
27 | chmod +x .git/hooks/pre-commit
28 | fi
29 | if [ -f build-aux/git-hooks/commit-msg -a ! -f .git/hooks/commit-msg ] ; then
30 | cat <&2
31 | *** Activating commit log message check hook. ***
32 | EOF
33 | cp -av build-aux/git-hooks/commit-msg .git/hooks/commit-msg
34 | chmod +x .git/hooks/commit-msg
35 | fi
36 | fi
37 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.1991.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | PGP Message Exchange Formats
7 |
8 | MIT
9 |
10 |
11 | 12 Rindge Ave. #1R
12 | Cambridge
13 | MA
14 | 02140
15 | US
16 | +1 617 868 4469
17 | warlord@MIT.EDU
18 |
19 | Comp-Comm Consulting
20 |
21 |
22 | P. O. Box 2405
23 | Brewster
24 | MA
25 | 02631
26 | US
27 | stallings@ACM.org
28 |
29 | Boulder Software Engineering
30 |
31 |
32 | 3021 Eleventh Street
33 | Boulder
34 | CO
35 | 80304
36 | US
37 | +1 303 541 0140
38 | prz@acm.org
39 |
40 |
41 |
42 |
43 |
44 |
--------------------------------------------------------------------------------
/web/news.en.rss:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 | GnuPG.org
5 | http://www.gnupg.org/
6 | Latest news about GNU Privacy Guard encryption software.
7 | Copyright 1998--2014 The GnuPG Project
8 | Fri, 11 Apr 2014 10:00:00 GMT
9 | en
10 | wk@gnupg.org
11 | webmaster@gnupg.org
12 | handcrafted
13 | 1200
14 | http://feedvalidator.org/docs/rss2.html
15 |
16 | http://www.gnupg.org/share/gnupg-lock-20x25tr.png
17 | GnuPG.org
18 | http://www.gnupg.org/
19 | 2025
20 | GnuPG's logo
21 |
22 |
23 |
24 | GnuPG 1.4.16 released
25 | Wed, 18 Dec 2013 12:00:00 GMT
26 | Werner Koch <wk@gnupg.org>
27 |
28 | Along with the publication of an interesting new side channel attack
29 | by Genkin, Shamir, and Tromer we announce the availability of a new
30 | stable GnuPG release to relieve this bug: Version 1.4.16 ...
31 |
32 | http://lists.gnupg.org/pipermail/gnupg-announce/2013q4/000337.html
33 | http://lists.gnupg.org/pipermail/gnupg-announce/2013q4/000337.html
34 |
35 |
36 |
37 |
38 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.1951.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | DEFLATE Compressed Data Format Specification version 1.3
7 |
8 | Aladdin Enterprises
9 |
10 |
11 | 203 Santa Margarita Ave.
12 | Menlo Park
13 | CA
14 | 94025
15 | US
16 | +1 415 322 0103
17 | +1 415 322 1734
18 | ghost@aladdin.com
19 |
20 |
21 | This specification defines a lossless compressed data format that compresses data using a combination of the LZ77 algorithm and Huffman coding, with efficiency comparable to the best currently available general-purpose compression methods. The data can be produced or consumed, even for an arbitrarily long sequentially presented input data stream, using only an a priori bounded amount of intermediate storage. The format can be implemented readily in a manner not covered by patents.
22 |
23 |
24 |
25 |
26 |
27 |
28 |
--------------------------------------------------------------------------------
/misc/blog.gnupg.org/20140206-crowdfunding-complete.org:
--------------------------------------------------------------------------------
1 | # Old blog post converted from HTML to ORG.
2 | #+STARTUP: showall
3 | #+AUTHOR: Sam Tuke
4 | #+DATE: 6th February 2014
5 |
6 | *** Mission complete: campaign ends, closing stats
7 |
8 | #+CAPTION: Today's donation totals
9 | [[file:img/funding-chart.png]]
10 |
11 |
12 | After 50 days of crowdfunding, the [[http://goteo.org/project/gnupg-new-website-and-infrastructure][GnuPG campaign]] for new website and
13 | infrastructure will close tomorrow. That means rewards for backers can
14 | now be ordered and preparations for dispatch can begin. Here are the
15 | results so far:
16 |
17 | - 36.741 EUR raised out of 24.000 target
18 | - 1.081 people donated in support
19 | - 350 EUR Largest single donation
20 | - 33 EUR average donation
21 | - 365 Stickers claimed
22 | - 300 T-shirts claimed
23 | - 191 GnuPG email addresses claimed
24 | - 793 Additional Twitter followers (from 60)
25 |
26 | Goteo, the Free Software platform hosting the campaign, usually required
27 | two 40 day rounds of funding, but in our case we're ending early, after
28 | just 50 days. This will enable us to deliver the new site and GnuPG 2.1
29 | faster, and is possible thanks to reaching our goal so quickly (in just
30 | 26 hours).
31 |
32 | We're currently preparing a system for collecting donor preferences for
33 | their rewards (sizes, addresses, etc.), so expect to be contacted in the
34 | next week or two if that includes you.
35 |
36 | Thanks again to all our backers for the overwhelming support that GnuPG
37 | has received!
38 |
--------------------------------------------------------------------------------
/web/aegypten/time.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - Project Ägypten - Schedule
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 |
5 | * Project Ägypten: Schedule
6 |
7 | [[file:index.org][Home]] | [[file:tech.org][Technology]] | [[file:who.org][Who]] | Schedule | [[file:development.org][Development]] |
8 | [[file:pr.org][Public Relations]] | [[file:glossary.org][Glossary]]
9 |
10 |
11 | The project is in the cleanup and maintenance phase. Upcoming bugs will
12 | be investigated.
13 |
14 | ** Completed
15 |
16 | Milestone 6, (27-November-2002, planned was end of August): Project
17 | accepted.
18 |
19 | Milestone 5 (1-August-2002): External test finished.
20 |
21 | Milestones 4.1 and 4.2 (29-April-2002): Smartcard connection, PKCS-15,
22 | KMail address book is connected, Presentation at CeBIT
23 | (13-20-March-2002), Integration in mutt.
24 |
25 | Milestone 3 (19-February-2002): LDAP connection for CRL retrieval
26 | finished, creation and management for keys are integrated in KMail user
27 | interface. OpenPGP in KMail works analogous to S/MIME.
28 |
29 | Planning of milestones revised (14-January-2002).
30 |
31 | Milestone 2 (21-December-2001, planned was 26-November): Encryption,
32 | decryption, signing and signature checking works for KMail
33 |
34 | Milestone 1 (29-October-2001): Implementation design and interface
35 | definitions ready to start implementation work
36 |
37 |
38 |
39 |
40 | (C) Intevation, Verbatim copying and distribution of this entire page
41 | is permitted in any medium, provided this notice is preserved.
42 | #+HTML:
43 |
--------------------------------------------------------------------------------
/web/share/3rdparty/bcswipe.js:
--------------------------------------------------------------------------------
1 | /**
2 | * Bootstrap Carousel Swipe v1.1
3 | *
4 | * jQuery plugin to enable swipe gestures on Bootstrap 3 carousels.
5 | * Examples and documentation: https://github.com/maaaaark/bcSwipe
6 | *
7 | * Licensed under the MIT license.
8 | */
9 | (function($) {
10 | $.fn.bcSwipe = function(settings) {
11 | var config = { threshold: 50 };
12 | if (settings) {
13 | $.extend(config, settings);
14 | }
15 |
16 | this.each(function() {
17 | var stillMoving = false;
18 | var start;
19 |
20 | if ('ontouchstart' in document.documentElement) {
21 | this.addEventListener('touchstart', onTouchStart, false);
22 | }
23 |
24 | function onTouchStart(e) {
25 | if (e.touches.length == 1) {
26 | start = e.touches[0].pageX;
27 | stillMoving = true;
28 | this.addEventListener('touchmove', onTouchMove, false);
29 | }
30 | }
31 |
32 | function onTouchMove(e) {
33 | if (stillMoving) {
34 | var x = e.touches[0].pageX;
35 | var difference = start - x;
36 | if (Math.abs(difference) >= config.threshold) {
37 | cancelTouch();
38 | if (difference > 0) {
39 | $(this).carousel('next');
40 | }
41 | else {
42 | $(this).carousel('prev');
43 | }
44 | }
45 | }
46 | }
47 |
48 | function cancelTouch() {
49 | this.removeEventListener('touchmove', onTouchMove);
50 | start = null;
51 | stillMoving = false;
52 | }
53 | });
54 |
55 | return this;
56 | };
57 | })(jQuery);
58 |
--------------------------------------------------------------------------------
/misc/jenkins/bin/make-windows-cd.sh:
--------------------------------------------------------------------------------
1 | #!/bin/sh
2 |
3 | set -ex
4 |
5 | if ! [ -f config.log ] || ! grep -q mingw config.log; then
6 | echo "must be run from a configured windows build environment"
7 | fi
8 |
9 | [ -z "$w32root" ] && w32root="$HOME/w32root"
10 | ADDITIONAL_FILES=
11 | IMAGE=gnupg-test.iso
12 | XTEST_GPGME_SRCDIR=$HOME/src/gpgme-for-gnupgs-tests
13 | XTEST_GPGME_BUILDDIR=$HOME/src/gpgme-for-gnupgs-tests/obj.w32
14 |
15 | [ -f make-windows-cd.rc ] && . make-windows-cd.rc
16 |
17 | # we pick binaries from the prefix, so make sure they are current.
18 | make install
19 |
20 | WORKDIR="$(mktemp --directory)"
21 | TARGET="${WORKDIR}/gnupg"
22 |
23 | mkdir "$TARGET"
24 |
25 | [ "$ADDITIONAL_FILES" ] && cp -v $(ls -1 $ADDITIONAL_FILES) $TARGET
26 | cp -v $w32root/bin/*.exe $w32root/bin/*.dll $TARGET
27 | cp -v tests/gpgscm/*.exe $TARGET
28 | # XXX mk-tdata is on the way out
29 | cp -v tools/mk-tdata.exe $TARGET || true
30 | cp -v agent/gpg-preset-passphrase.exe $TARGET
31 | cp -v -a ../tests $TARGET
32 | if [ -e "$XTEST_GPGME_SRCDIR" ] && [ -e "$XTEST_GPGME_BUILDDIR" ]; then
33 | cp -a "$XTEST_GPGME_SRCDIR" $TARGET/gpgme
34 | cp -v "$XTEST_GPGME_BUILDDIR"/src/.libs/*.exe $TARGET
35 | cp -v "$XTEST_GPGME_BUILDDIR"/src/.libs/*.dll $TARGET
36 | # Strip .git.
37 | rm -rf -- $TARGET/gpgme/.git
38 | # Remove native build if it exists.
39 | rm -rf -- $TARGET/gpgme/obj
40 | fi
41 | cp -v -a ../tests $TARGET
42 | cp -v tests/openpgp/fake-pinentry.exe $TARGET
43 | cp -v /home/jenkins/bin/run-tests.bat $WORKDIR
44 | [ -f "$IMAGE" ] && rm -f "$IMAGE"
45 | genisoimage --output "$IMAGE" -J "$WORKDIR"
46 | [ "${WORKDIR}" ] && rm -rf -- "${WORKDIR}"
47 |
--------------------------------------------------------------------------------
/web/download/supported_systems.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - Supported Systems
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 |
5 | * Supported Systems
6 |
7 | GnuPG works very well on almost all 32 and 64 bit platforms.
8 |
9 | It works fine on *GNU/Linux* with amd64, x86, alpha, mips, sparc64,
10 | armhf, arm64, m68k, or PowerPC CPUs. (amd64 is the primary development system, the other
11 | CPUs are only checked from time to time.)
12 |
13 | 64 bit versions of *Windows* 10 and 11 are very well supported.
14 |
15 | *MacOS X* is also supported; please see [[https://gpgtools.org/][gpgtools.org]] for detailed
16 | information.
17 |
18 | *OpenBSD*, *FreeBSD*, *NetBSD*, *AIX*, and *Solaris* are fully supported.
19 |
20 | ** Other OSes
21 |
22 | *The information in this section is considered outdated!*
23 |
24 | It compiles okay on *GNU/Hurd* but because Mach has no random
25 | device, it should not be used for real work. Work is underway to add
26 | an random device.
27 |
28 | A port of GnuPG to *VMS* is available at
29 | [[http://antinode.info/dec/sw/gnupg.html][http://antinode.info/dec/sw/gnupg.html]].
30 |
31 | GnuPG compiles and runs on many more systems, but due to the lack
32 | of a well tested entropy source, it /should be used with some
33 | caution/. We have positive reports on these systems:
34 |
35 | - *BSDI* v4.0.1 with i386
36 | - *HPUX* v9.x, v10.x and v11.0 with HPPA CPU
37 | - *IRIX* v6.3 with MIPS R10000 CPU
38 | - *MP-RAS* v3.02
39 | - *OSF1* V4.0 with Alpha CPU
40 | - *OS/2* version 2
41 | - *SCO* UnixWare/7.1.0
42 | - *SunOS* on Sparc and x86
43 | - *USL Unixware* v1.1.2
44 |
--------------------------------------------------------------------------------
/web/software/gpa/icons.org:
--------------------------------------------------------------------------------
1 | #+STARTUP: showall
2 | #+SETUPFILE: "../../share/setup.inc"
3 |
4 | * GPA - Icons
5 |
6 | Here it is described in detail what is the meaning of the icons that
7 | you can find in GPA.
8 |
9 | ** Sign
10 |
11 | [[file:icons/sign.png]] With your secret key (always shown in yellow) you
12 | can sign files or public keys. To check your signature people need
13 | your public key (and of course they should trust it).
14 |
15 | ** Encrypt
16 |
17 | [[file:icons/encrypt.png]] With someone's public key you can encrypt a file.
18 | Only the corresponding secret key can decrypt the file.
19 |
20 | ** Decrypt
21 |
22 | [[file:icons/decrypt.png]] With your secret key you can decrypt any document
23 | that was encrypted for you (using your public key).
24 |
25 | ** Keyring
26 |
27 | [[file:icons/keyring.png]] In your public keyring you hold public keys of
28 | people you want to send encrypted documents. The keyring also
29 | supports you to judge the trust in other keys which ultimately
30 | leads to trust identification for signatures you encounter in
31 | files, emails and other documents.
32 |
33 | ** Ownertrust
34 |
35 | [[file:icons/dont_trust.png]] [[file:icons/trust_fully.png]]
36 | [[file:icons/trust_marginally.png]] [[file:icons/trust_unknown.png]]
37 |
38 | This value describes your opinion about the other ones ability to
39 | correctly sign other keys. Your personal trust in the owner of a
40 | public key varies from full trust (thumb up) over marginal trust
41 | (thumb horizontal) to no trust (thumb down). If you have no opinion
42 | about the person, you can leave the ownertrust unknown.
43 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.4880.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | OpenPGP Message Format
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 | This document is maintained in order to publish all necessary information needed to develop interoperable applications based on the OpenPGP format. It is not a step-by-step cookbook for writing an application. It describes only the format and methods needed to read, check, generate, and write conforming packets crossing any network. It does not deal with storage and implementation questions. It does, however, discuss implementation issues necessary to avoid security flaws.</t><t> OpenPGP software uses a combination of strong public-key and symmetric cryptography to provide security services for electronic communications and data storage. These services include confidentiality, key management, authentication, and digital signatures. This document specifies the message formats used in OpenPGP. [STANDARDS-TRACK]
20 |
21 |
22 |
23 |
24 |
--------------------------------------------------------------------------------
/web/faq/why-not-idea.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - Why not IDEA
2 |
3 | * Update
4 |
5 | Note that the IDEA patent has expired and IDEA is now directly
6 | supported since GnuPG 1.4.13 respective 2.x with Libgcrypt 1.6. The
7 | use of IDEA is not suggested due to its short block length and it is
8 | only provided to allow decryption of archived data.
9 |
10 | The section below is thus only of historic interest.
11 |
12 |
13 | * Why not IDEA
14 |
15 | IDEA is a patented algorithm and therefore the use of IDEA in
16 | countries where this patent is valid can not be allowed due to
17 | restrictions in the GNU General Public License. Those restrictions are
18 | there to help protecting the freedom of software.
19 |
20 | For more information on the nonsense of software patents and the
21 | general problem with this, please see [[www.noepatents.org]].
22 |
23 | If you still want to use IDEA and you are legally allowed to do so,
24 | you can download the [[ftp://ftp.gnupg.dk/contrib-dk/idea.c.gz][idea.c.gz]] file and its [[ftp://ftp.gnupg.dk/contrib-dk/idea.c.gz.sig][signature]] , read
25 | the instructions at the top of the file, compile it and use it as a
26 | plugin for GnuPG. But please do us all a favor and use it only for
27 | decrypting. CAST5 and AES are good and patent unencumbered algorithms
28 | which don't bear any interoperability problems.
29 |
30 | Windows user might be interested in the [[ftp://ftp.gnupg.dk/contrib-dk/ideadll.zip][precompiled DLL]] and its
31 | [[ftp://ftp.gnupg.dk/contrib-dk/ideadll.zip.sig][signature]].
32 |
33 |
34 | # Copyright (C) 2002-2004 Free Software Foundation, Inc.
35 | #
36 | # Written by Werner Koch (2002-07-15 22:10).
37 |
--------------------------------------------------------------------------------
/web/oids.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - OID Registry
2 | #+STARTUP: showall
3 |
4 | * OID Registry
5 |
6 | The OID 1.3.6.1.4.1.11591 has been assigned to the GNU project. The
7 | list below shows only the OIDs relevant for GnuPG. You find the
8 | definitive list in the [[http://www.gnu.org/prep/standards/html_node/OID-Allocations.html][GNU Standards document]].
9 |
10 | - 1.3.6.1.4.1.11591.2 :: GnuPG (Ägypten)
11 |
12 | - 1.3.6.1.4.1.11591.2.1 :: notation
13 |
14 | - 1.3.6.1.4.1.11591.2.1.1 :: pkaAddress
15 |
16 | - 1.3.6.1.4.1.11591.2.12242973 :: Invalid encoded OID
17 |
18 | - 1.3.6.1.4.1.11591.12 :: digestAlgorithm
19 |
20 | - 1.3.6.1.4.1.11591.12.2 :: TIGER/192
21 |
22 | - 1.3.6.1.4.1.11591.13 :: encryptionAlgorithm
23 |
24 | - 1.3.6.1.4.1.11591.13.2 :: Serpent
25 |
26 | - 1.3.6.1.4.1.11591.13.2.1 :: Serpent-128-ECB
27 | - 1.3.6.1.4.1.11591.13.2.2 :: Serpent-128-CBC
28 | - 1.3.6.1.4.1.11591.13.2.3 :: Serpent-128-OFB
29 | - 1.3.6.1.4.1.11591.13.2.4 :: Serpent-128-CFB
30 | - 1.3.6.1.4.1.11591.13.2.21 :: Serpent-192-ECB
31 | - 1.3.6.1.4.1.11591.13.2.22 :: Serpent-192-CBC
32 | - 1.3.6.1.4.1.11591.13.2.23 :: Serpent-192-OFB
33 | - 1.3.6.1.4.1.11591.13.2.24 :: Serpent-192-CFB
34 | - 1.3.6.1.4.1.11591.13.2.41 :: Serpent-256-ECB
35 | - 1.3.6.1.4.1.11591.13.2.42 :: Serpent-256-CBC
36 | - 1.3.6.1.4.1.11591.13.2.43 :: Serpent-256-OFB
37 | - 1.3.6.1.4.1.11591.13.2.44 :: Serpent-256-CFB
38 |
39 | - 1.3.6.1.4.1.11591.14 :: CRC algorithms
40 |
41 | - 1.3.6.1.4.1.11591.14.1 :: CRC 32
42 |
43 | - 1.3.6.1.4.1.11591.15 :: ellipticCurves
44 |
45 | - 1.3.6.1.4.1.11591.15.1 :: Ed25519
46 |
47 |
48 | You can search for OIDs at [[http://www.alvestrand.no/objectid/][Alvestrand]] .
49 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.1950.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | ZLIB Compressed Data Format Specification version 3.3
7 |
8 | Aladdin Enterprises
9 |
10 |
11 | 203 Santa Margarita Ave.
12 | Menlo Park
13 | CA
14 | 94025
15 | US
16 | +1 415 322 0103
17 | +1 415 322 1734
18 | ghost@aladdin.com
19 |
20 |
21 |
22 |
23 | This specification defines a lossless compressed data format. The data can be produced or consumed, even for an arbitrarily long sequentially presented input data stream, using only an a priori bounded amount of intermediate storage. The format presently uses the DEFLATE compression method but can be easily extended to use
24 | other compression methods. It can be implemented readily in a manner not covered by patents. This specification also defines the ADLER-32 checksum (an extension and improvement of the Fletcher checksum), used for detection of data corruption, and provides an algorithm for computing it.
25 |
26 |
27 |
28 |
29 |
30 |
31 |
--------------------------------------------------------------------------------
/misc/jenkins/bin/run-tests-w32.bash:
--------------------------------------------------------------------------------
1 | #!/bin/bash
2 |
3 | # Locking.
4 | exec 9<"$0"
5 | echo -n "Aquiring lock on $0... "
6 | if ! flock --timeout 15 9 ; then
7 | echo "failed!"
8 | exit 1
9 | fi
10 | echo "ok."
11 |
12 | set -ex
13 |
14 | URI="qemu:///system"
15 | GUEST="win8.1"
16 | GUEST_CDROM="sda"
17 | SSH="gpg@192.168.122.117"
18 | SSH_COMMAND_TIMEOUT="60m"
19 |
20 | function vdo() {
21 | virsh -c "$URI" "$@"
22 | }
23 |
24 | function vssh() {
25 | # OpenSSH on Windows does not cope well with a closed stdin.
26 | timeout /dev/null 2>&1 -oConnectTimeout=1 \
31 | "$SSH" "echo pong" ; then
32 | return 0
33 | else
34 | return 1
35 | fi
36 | }
37 |
38 | function vwait() {
39 | echo >&2 -n "Waiting for the machine to boot... "
40 | while ! vping ; do echo >&2 -n . ; sleep 1 ; done
41 | }
42 |
43 | # Revert to current snapshot and start the machine.
44 | vdo snapshot-revert --snapshotname tests --force --running "$GUEST"
45 |
46 | # Insert the CD.
47 | vdo change-media --update "$GUEST" "$GUEST_CDROM" "$1"
48 |
49 | set +x
50 | vwait
51 | set -x
52 |
53 | #sleep 5 # XXX: Let things settle.
54 |
55 | if [ "$2" ]; then
56 | scp "$2" "$SSH:"
57 | sleep 5 # XXX: openssh on windows is a bit fragile...
58 | time vssh "cmd /c $(basename $2)"
59 | else
60 | time vssh "cmd /c d:/run-tests.bat"
61 | fi
62 |
63 | sleep 5 # XXX: openssh on windows is a bit fragile...
64 |
65 | # The scp server is a bit fragile as well, and I believe globbing does
66 | # not work. Simply use gpgtar.
67 | vssh 'powershell -Command "cd c:\temp\logs ; d:/gnupg/gpgtar.exe --create ."' | tar x --warning=no-timestamp
68 |
69 | # Shutdown.
70 | vdo shutdown "$GUEST"
71 |
--------------------------------------------------------------------------------
/web/software/gpa/index.org:
--------------------------------------------------------------------------------
1 | #+STARTUP: showall
2 | #+SETUPFILE: "../../share/setup.inc"
3 |
4 | * GPA - The Gnu Privacy Assistant
5 |
6 | The /GNU Privacy Assistant/ (GPA) is a graphical user interface for
7 | the [[../../index.en.html][GnuPG]] (GNU Privacy Guard).
8 |
9 | GPA utilizes [[http://www.gtk.org][GTK+]] (the GIMP Tool Kit) and compiles for various
10 | platforms. You can have a look at some [[file:screenshots.org][screenshots]] . You can learn
11 | more about GPA [[file:icons.org][icons]], as well.
12 |
13 | GPA is available at the [[ftp://ftp.gnupg.org/gcrypt/gpa//][GnuPG FTP server]] and its mirrors.
14 |
15 | ** Changes in version 0.10.0 (2018-10-16)
16 |
17 | - Added key manager context menu items to copy the key fingerprint
18 | and the secret key to the clipboard.
19 | - Added "Details" buttons to many error popups to show raw
20 | diagnostic output from gpg.
21 | - Changed the "Retrieve Key" dialog to first try the Web Key
22 | Directory if a mail address is given. Only if this lookup fails
23 | the keyservers are searched.
24 | - Added a user-ID notebook page to show per user-ID info.
25 | - Made location of locale dir under Windows more flexible.
26 | - Fixed crash on filename conversion error. [[[https://dev.gnupg.org/T2185][#2185]]]
27 | - Fixed listing of key algos in the subkey windows. [[[https://dev.gnupg.org/T3405][#3405]]]
28 | - Removed lazy loading of the secret keyring. [[[https://dev.gnupg.org/T3748][#3748]]]
29 |
30 | ** Changes in version 0.9.10 (2016-11-19)
31 |
32 | - Added basic support for TOFU information.
33 | - Removed key-ID from some listings in favor of using the
34 | fingerprint.
35 | - Fixed deletion of X.509 keys.
36 | - Allow for saving to an alternate file name if the file already
37 | exists.
38 | - Fixed several problems with key edit functions.
39 | - Fixed drag-and-drop.
40 |
--------------------------------------------------------------------------------
/misc/blog.gnupg.org/20131218-getting-goteo-approval.org:
--------------------------------------------------------------------------------
1 | # Old blog post converted from HTML to ORG.
2 | #+STARTUP: showall
3 | #+AUTHOR: Sam Tuke
4 | #+DATE: 18th December 2013
5 |
6 | ** Getting Goteo approval
7 |
8 | #+CAPTION: Pending project on Goteo
9 | [[file:img/goteo-review.png]]
10 |
11 | The targets are set, the rewards are prepared, the press release has
12 | been edited and translated, and now we're waiting for approval from the
13 | crowdfunding platform [[http://goteo.org/][Goteo]].
14 |
15 | Goteo is like indiegogo, but more forward thinking. It has a special
16 | focus on communal benefits and rewards - projects that benefit society
17 | as a whole, not just project donors (though they can get special rewards
18 | too).
19 |
20 | Every 'good' produced by a campaign on Goteo, be it artwork, software,
21 | event, or manufactured product, has a license assigned to it, like GPL
22 | or Creative Commons, and as well as asking for money, projects ask for
23 | other forms of help called “non-economic needs”, like translations or
24 | product testing. Goteo's [[https://github.com/Goteo/Goteo][own source]]
25 | code is Free Software too, meaning anyone can run their own Goteo
26 | crowdfunding server. That's the feature that swung our decision to use
27 | it for GnuPG.
28 |
29 | Because the type of project on Goteo is quite specific however, the
30 | acceptance phase of launching crowdfunding is taking us longer than
31 | expected. Right now we're working with Goteo's small team to answer
32 | questions which aren't on the webforms you fill out when you design your
33 | project with their system.
34 |
35 | I'm hoping to provide what's necesasry and get acceptance quickly. As
36 | soon as we have it the crowdfunding will launch and [[http://gnupg.hosted.phplist.com/lists/?p=subscribe&id=1][newsletter]]
37 | subscribers and [[https://twitter.com/gnupg][Twitter]] followers will be the first to know.
38 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.2119.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | Key words for use in RFCs to Indicate Requirement Levels
7 |
8 | Harvard University
9 |
10 |
11 | 1350 Mass. Ave.
12 | Cambridge
13 | MA 02138
14 | - +1 617 495 3864
15 | sob@harvard.edu
16 |
17 | General
18 | keyword
19 |
20 |
21 | In many standards track documents several words are used to signify
22 | the requirements in the specification. These words are often
23 | capitalized. This document defines these words as they should be
24 | interpreted in IETF documents. Authors who follow these guidelines
25 | should incorporate this phrase near the beginning of their document:
26 |
27 |
28 |
29 | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
30 | NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
31 | "OPTIONAL" in this document are to be interpreted as described in
32 | RFC 2119.
33 |
34 |
35 | Note that the force of these words is modified by the requirement
36 | level of the document in which they are used.
37 |
38 |
39 |
40 |
41 |
42 |
43 |
44 |
45 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.6189.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | ZRTP: Media Path Key Agreement for Unicast Secure RTP
6 |
7 |
8 |
9 |
10 | This document defines ZRTP, a protocol for media path Diffie-Hellman exchange to agree on a session key and parameters for establishing unicast Secure Real-time Transport Protocol (SRTP) sessions for Voice over IP (VoIP) applications. The ZRTP protocol is media path keying because it is multiplexed on the same port as RTP and does not require support in the signaling protocol. ZRTP does not assume a Public Key Infrastructure (PKI) or require the complexity of certificates in end devices. For the media session, ZRTP provides confidentiality, protection against man-in-the-middle (MiTM) attacks, and, in cases where the signaling protocol provides end-to-end integrity protection, authentication. ZRTP can utilize a Session Description Protocol (SDP) attribute to provide discovery and authentication through the signaling channel. To provide best effort SRTP, ZRTP utilizes normal RTP/AVP (Audio-Visual Profile) profiles. ZRTP secures media sessions that include a voice media stream and can also secure media sessions that do not include voice by using an optional digital signature. This document is not an Internet Standards Track specification; it is published for informational purposes.
11 |
12 |
13 |
14 |
15 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.5226.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | Guidelines for Writing an IANA Considerations Section in RFCs
7 |
8 |
9 |
10 |
11 |
12 |
13 | Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication transform for IPsec). To ensure that such quantities have consistent values and interpretations across all implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA).</t><t> In order for IANA to manage a given namespace prudently, it needs guidelines describing the conditions under which new values can be assigned or when modifications to existing values can be made. If IANA is expected to play a role in the management of a namespace, IANA must be given clear and concise instructions describing that role. This document discusses issues that should be considered in formulating a policy for assigning values to a namespace and provides guidelines for authors on the specific text that must be included in documents that place demands on IANA.</t><t> This document obsoletes RFC 2434. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
14 |
15 |
16 |
17 |
18 |
19 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.4086.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | Randomness Requirements for Security
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 | Security systems are built on strong cryptographic algorithms that foil pattern analysis attempts. However, the security of these systems is dependent on generating secret quantities for passwords, cryptographic keys, and similar quantities. The use of pseudo-random processes to generate secret quantities can result in pseudo-security. A sophisticated attacker may find it easier to reproduce the environment that produced the secret quantities and to search the resulting small set of possibilities than to locate the quantities in the whole of the potential number space.</t><t> Choosing random quantities to foil a resourceful and motivated adversary is surprisingly difficult. This document points out many pitfalls in using poor entropy sources or traditional pseudo-random number generation techniques for generating such quantities. It recommends the use of truly random hardware techniques and shows that the existing hardware on many systems can be used for this purpose. It provides suggestions to ameliorate the problem when a hardware solution is not available, and it gives examples of how large such quantities need to be for some applications. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
16 |
17 |
18 |
19 |
20 |
21 |
--------------------------------------------------------------------------------
/misc/blog.gnupg.org/update-index.sh:
--------------------------------------------------------------------------------
1 | #!/bin/sh
2 | # Insert the ctual index into index.html
3 |
4 | pgm=update-index.sh
5 |
6 | if [ ! -f index.html ]; then
7 | echo "$pgm: blog.gnupg.org/index.html has not been build" >&2
8 | exit 1
9 | fi
10 |
11 | # Find all rendered HTML files but skip possible translated versions.
12 | find . -maxdepth 1 -type f -name "20*.html" -print \
13 | | grep -v '\.[a-z][a-z].html$' | sort -r >index.tmp
14 | newest=$(head -1 index.tmp)
15 |
16 | # Extract the head lines
17 | : >index.headlines.tmp
18 | cat index.tmp | while read fname; do
19 | echo -n "${fname#./}|" >>index.headlines.tmp
20 | sed -n '/^
"
54 | close (file)
55 | }
56 | '
57 | if ! mv index.tmp index.html ; then
58 | echo "$pgm: error updating blog index" >&2
59 | exit 1
60 | fi
61 |
62 | # FIXME: Create a feed file
63 |
64 | # Rename headlines file
65 | mv index.headlines.tmp headlines.txt
66 |
67 | exit 0
68 |
--------------------------------------------------------------------------------
/misc/id/eddsa-for-openpgp/template.xml:
--------------------------------------------------------------------------------
1 |
2 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
15 |
16 | ]>
17 |
18 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 | EdDSA for OpenPGP
31 |
33 | g10 Code
34 |
35 | wk@gnupg.org
36 | https://g10code.com
37 |
38 |
39 |
40 |
41 | Security
42 |
43 |
44 | &pandocAbstract;
45 |
46 |
47 |
48 |
49 | &pandocMiddle;
50 |
51 |
52 |
53 |
54 | &eddsa;
55 | &rfc.4880;
56 | &rfc.6637;
57 | &rfc.5226;
58 | &rfc.2119;
59 |
60 |
61 | &ed25519;
62 | &rfc.7748;
63 |
64 | &pandocBack;
65 |
66 |
67 |
--------------------------------------------------------------------------------
/web/share/data-privacy-key.asc:
--------------------------------------------------------------------------------
1 | pub rsa2048 2018-05-16 [SC] [expires: 2028-02-25]
2 | DC3629A4DBD434211589A0E1EB6CA96502867BDA
3 | uid [ultimate] data-privacy@gnupg.org
4 | sub rsa2048 2018-05-16 [E]
5 | AB9897AC6DAAB01680F6C8FFC36EBD049AEA1BAA
6 |
7 |
8 | -----BEGIN PGP PUBLIC KEY BLOCK-----
9 |
10 | mQENBFr72M0BCADzDmCPrvQWm/aObH6mGkPZdAtaiTTpHh0/okXcCSYdofjqXJe/
11 | myBHj1eMZ5MO29+lahmDiwsb2v+JAxYzKc76DhBVv1Ee5/GmNH27bmERC2sS3KO6
12 | pae43aXf1xsdOjXw0BthS1CZZ4MNukUzpUVeeo2GkThFy3v1HHzgTPUcGSzN7LUl
13 | 8X0+PyX+N0Y0S4sWsVOadyj0PokP/L8+zHnBQP3UkjBwahAEM9YQ2EDiUak1UK5S
14 | 4t50+q43vPikfohEDm/Tk0A6lU7Q3KUyIlS/rjwzPn/ZA1o02Xehyl3odp6aUFVB
15 | D5xW98SF3PgYvgAxAMXx21PPnQ0Ai8W2oTgXABEBAAG0FmRhdGEtcHJpdmFjeUBn
16 | bnVwZy5vcmeJAVQEEwEIAD4CGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AWIQTc
17 | Nimk29Q0IRWJoOHrbKllAoZ72gUCZdySNQUJEmWHaAAKCRDrbKllAoZ72vVBCACB
18 | ra4/NQvhPtlnu3ZTUD3h7rwjkjkr7iIw2R4ssG8yTbFifFXFmjd+VQxT3NQjIjfv
19 | fAnyFwD38nKM7jD5RpHwlt0INL/91tIoF21KTtvfzZdKVaRy5BEtjKtjLggtU+wH
20 | iMxdQiePLok+235MRliD8KCb1KzAy2OcsMn0IBPz5SjaouORN9BhHF+jAcifGYo9
21 | EZv5KXYiDihPZ87wQ+WNQRfmfLEMYN4MEcSh6Z8tBx8NZU49e1d5a2lduHQap6CE
22 | qNsnBvpfKCzrKo1lJiAjtR2E1whlu1ypyxyiWXCShGGj5cTDfGgzHxaNkGBpYirV
23 | mZuBuxeR8sxPReleKEz5uQENBFr72M0BCADCTuMKyGLoj5nmCmYHO9hOnGt3qVEF
24 | 9g4UvOIu/REl/gLNRFOcGqqmDyJjeo77syHqQVI98yc4JOr74tdPvr2rS22Hmuv3
25 | CCcFhSDT32kV6l8eTgB5SB6Ap+q63OuFBwAEVnJqf5TzvYdGsGQSrFgoEinp1upa
26 | E5tSknF0EEPrC+htDh845+YtAXPcDcIvZZHb6irG629Jl6BgnNJaL2xHxxtcLm6H
27 | g92PACiOVmdThTk15PKDAznYtHmxu5jRUF5+KWT/E6N8FFr6aYRvPK7KctRRDJMm
28 | fqijnsXvELZav5MBnW27cnGL5nTjYXEdzFOLghAT2qotyJjmjOVIvqF5ABEBAAGJ
29 | ATYEGAECACAWIQTcNimk29Q0IRWJoOHrbKllAoZ72gUCWvvYzQIbDAAKCRDrbKll
30 | AoZ72rwpB/9bHDd3h3M7+2IEnl4WnbMUUTN6TiGc+vBulNPnTjeOp2+6p+j79HYD
31 | LPrOZo4nYz0GBwbWe91W8p9li5VYAs2WLXnJ1nLfll/mrA6OxWLwW7VotSeFLInz
32 | vxPGlLbI6mEJ3L6PyLNCd6buGEIyVoJNkUAVSOjuVby1BZJftItWH3q5drTLkQzg
33 | mJ8h+ctQxDkn0UD4LWzEmE55ieLH0ySnVzY7nOzGtcE/IjzgtuRllkoNZmc22VOk
34 | EvTeR84kdIntwk6nb2St8qMnN9ea81/iDNSCt9xkz/HMN5WAjLTYqr7LSQrUTae1
35 | /r7eE98xbr4BrOpjQOefGkVreSPcJHT9
36 | =hMOJ
37 | -----END PGP PUBLIC KEY BLOCK-----
38 |
--------------------------------------------------------------------------------
/web/donate/index.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - Donate
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 | #
5 | # Note: Do not use relative links because this page is also used as a
6 | # template from cgi-bin/. Using https://www.gnupg.org/... is
7 | # fine as it is stripped before publishing.
8 |
9 |
10 | * GnuPG used to ask for your support to help protect online privacy
11 |
12 | Activists, journalists, lawyers, and many others rely on GnuPG to
13 | protect their communication. And, nearly all free software-based
14 | operating systems (which are used by more than two-thirds of the
15 | servers running the Internet) rely on GnuPG to verify the integrity
16 | of system updates.
17 |
18 | GnuPG development was mainly financed by donations. Aside of the
19 | large donors Linux Foundation, Stripe, Facebook, and First Look
20 | Media, we received a lot of individual donations. Our fundraising
21 | [[file:camp2017.org][campaign]] in 2017 also raised about 5000 Euro in monthly recurring
22 | donations.
23 |
24 | *Many thanks to all supporters*
25 |
26 | Fortunately, and this is still not common with free software, we
27 | have now established a way of financing the development while
28 | keeping all our software free and freely available for everyone.
29 |
30 | Our model is similar to the way RedHat manages RHEL and Fedora:
31 | Except for the actual binary of the MSI installer for Windows and
32 | client specific configuration files, all the software is available
33 | under the GNU GPL and other Open Source licenses. Thus customers
34 | may even build and distribute their own version of the software as
35 | long as they do not use our trademark /GnuPG VS-Desktop^{\reg}/.
36 |
37 | Those with *SEPA donations, please cancel them and redirect* your
38 | funds to other projects which are more in need of financial support.
39 | The donations done via Stripe or PayPal have already been canceled.
40 |
41 | All you supporters greatly helped us to keep GnuPG alive and to
42 | finally setup a sustainable development model. Stay tuned for a
43 | somewhat longer writeup on this.
44 |
45 | *Thanks.*
46 |
47 |
48 | # eof #
49 |
--------------------------------------------------------------------------------
/web/Makefile:
--------------------------------------------------------------------------------
1 | # Makefile for swdb
2 | #
3 | #
4 | # You need to have in ~/.gnupg-autogen.rc lines like this:
5 | #
6 | # VERSIONSGNUPG_CMD=scp
7 | # VERSIONSGNUPG_LOC=al-kindi.gnupg.org:/var/www/versions.gnupg.org/
8 | #
9 | #
10 |
11 | all: swdb.lst.sig
12 |
13 | swdb.lst-new: swdb.mac
14 | @awk ' \
15 | ! /^#\+macro:/ {next} \
16 | $$2 ~ /ftp_.*/ {next} \
17 | {print $$2, $$3, $$4, $$5} \
18 | ' swdb.mac | sed 's/[[:blank:]]*$$//' >swdb.lst-new
19 |
20 | swdb.lst.sig: swdb.lst-new
21 | @(set -e;\
22 | key=$$(grep '^SWDB_SIGNKEY=' $$HOME/.gnupg-autogen.rc|cut -d= -f2);\
23 | if [ -z "$$key" ]; then \
24 | echo "error: SWDB_SIGNKEY missing in ~/.gnupg-autogen.rc">&2; \
25 | exit 2;\
26 | fi;\
27 | ( mydir=`pwd`; cd /tmp; \
28 | git diff "$$mydir"/swdb.lst "$$mydir"/swdb.lst-new || true ); \
29 | echo "==================================";\
30 | echo -n "Enter \"yes\" if it is okay to sign: "; read yesno; \
31 | [ "$$yesno" = yes ] || exit 1;\
32 | mv -f swdb.lst-new swdb.lst ;\
33 | gpg -sbu "$$key" swdb.lst;\
34 | )
35 |
36 |
37 | signcheck: swdb.lst
38 | @set -e; \
39 | tmp="$$(awk '$$1~/^.*_ver/{print $$1}' swdb.lst \
40 | |sort|uniq -c|sort -nr|head -1|cut -b 1-7)"; \
41 | if [ "$$tmp" -ne 1 ]; then \
42 | echo "ERROR: Duplicate version numbers found" >&2; \
43 | exit 1; \
44 | fi
45 |
46 |
47 | upload: swdb.lst.sig signcheck
48 | +(set -e;\
49 | x=$$(grep '^VERSIONSGNUPG_CMD=' $$HOME/.gnupg-autogen.rc|cut -d= -f2|tr -d \');\
50 | if [ -z "$$x" ]; then \
51 | echo "error: VERSIONSGNUPG_CMD missing in ~/.gnupg-autogen.rc">&2;\
52 | exit 2;\
53 | fi;\
54 | mycmd="$$x";\
55 | x=$$(grep '^VERSIONSGNUPG_LOC=' $$HOME/.gnupg-autogen.rc|cut -d= -f2);\
56 | if [ -z "$$x" ]; then \
57 | echo "error: VERSIONSGNUPG_LOC missing in ~/.gnupg-autogen.rc">&2; \
58 | exit 2;\
59 | fi;\
60 | myloc="$$x";\
61 | $$mycmd swdb.lst.sig swdb.lst $$myloc \
62 | )
63 |
64 | .PHONY: upload all signcheck
65 |
--------------------------------------------------------------------------------
/misc/id/common/reference.RFC.1423.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | Privacy Enhancement for Internet Electronic Mail: Part III: Algorithms, Modes, and Identifiers
7 |
8 | Trusted Information Systems
9 |
10 |
11 | 3060 Washington Road
12 | Glenwood
13 | MD
14 | 21738
15 | US
16 | +1 301 854 6889
17 | balenson@tis.com
18 |
19 |
20 | This document provides definitions, formats, references, and citations for cryptographic algorithms, usage modes, and associated identifiers and parameters used in support of Privacy Enhanced Mail (PEM) in the Internet community. It is intended to become one member of the set of related PEM RFCs. This document is organized into four primary sections, dealing with message encryption algorithms, message integrity check algorithms, symmetric key management algorithms, and asymmetric key management algorithms (including both asymmetric encryption and asymmetric signature algorithms).
21 | Some parts of this material are cited by other documents and it is anticipated that some of the material herein may be changed, added, or replaced without affecting the citing documents. Therefore, algorithm-specific material has been placed into this separate document.
22 | Use of other algorithms and/or modes will require case-by-case study to determine applicability and constraints. The use of additional algorithms may be documented first in Prototype or Experimental RFCs. As experience is gained, these protocols may be considered for incorporation into the standard. Additional algorithms and modes approved for use in PEM in this context will be specified in successors to this document.
23 |
24 |
25 |
26 |
27 |
--------------------------------------------------------------------------------
/web/download/git.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - GIT Access
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 | #+GPGWEB-NEED-SWDB
5 |
6 | * GIT Access
7 |
8 | The GnuPG development is tracked using the Git distributed revision
9 | control system. A public read-only Git repository for GnuPG and
10 | related projects is available.
11 |
12 | This service is provided to help you in hunting bugs and not to
13 | deliver stable snapshots; it may happen that it even does not
14 | compile, so please don't complain. Git may put a high load on a
15 | server, so please don't poll for new pushes too often. Instead, we
16 | suggest you use notifications from
17 | https://dev.gnupg.org/source/gnupg.git which mirrors the
18 | repositories.
19 |
20 | There is a Web interface at [[https://git.gnupg.org/]] which can be used
21 | to browse the GIT repository.
22 |
23 | All repositories have been migrated to Git from the old Subversion
24 | (SVN) code management tool. The standard way you checkout from an
25 | anonymous GIT is to clone the entire repository from one of these
26 | repositories:
27 |
28 | #+BEGIN_EXAMPLE
29 | git clone https://dev.gnupg.org/source/gnupg.git
30 | git clone git://git.gnupg.org/gnupg.git
31 | #+END_EXAMPLE
32 |
33 | You must run =./autogen.sh= before running the =./configure= in the
34 | way suggested by the output of =autogen.sh=. This creates some
35 | required files which are not stored in the repository. =autogen.sh=
36 | also checks that you have all required tools installed. Please read
37 | the GIT manual pages before doing so. The current stable
38 | version is {{{gnupg24_ver}}} and known as {{{gnupg24_branch}}}; the
39 | long term support (LTS) version is {{{gnupg22_ver}}} and known as
40 | {{{gnupg22_branch}}}; the legacy 1.4 version of GnuPG
41 | ({{{gnupg1_ver}}}) is known as STABLE-BRANCH-1-4.
42 |
43 | Bug reports should go to the developers mailing list. See the page
44 | on [[../documentation/mailing-lists.org][mailing lists]] .
45 |
46 |
47 | ** Other Hosted Projects
48 |
49 | The GnuPG Git server also hosts some other projects in Git
50 | repositories. Please use the web interface at
51 | [[https://git.gnupg.org/]] to browse them.
52 |
--------------------------------------------------------------------------------
/web/software/libraries.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - Libraries
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 | #+OPTIONS: ^:{}
5 |
6 | * Libraries
7 |
8 | This page collects libraries related to GnuPG project.
9 |
10 | If you feel wanting to improve this list, please, fill in a [[https://www.gnupg.org/documentation/bts.html][Problem
11 | Report]] form.
12 |
13 | ** Libraries required to build GnuPG
14 |
15 | The libraries are required to build current GnuPG versions but may
16 | also be used on their own. They are maintained by the GnuPG Project.
17 |
18 | - [[file:libgpg-error/index.org][Libgpg-error]] :: Libgpg-error is a helper library used by a couple
19 | of other projects to provide a common set of
20 | error codes and descriptions.
21 | - [[file:libgcrypt/index.org][Libgcrypt]] :: Libgcrypt is a general purpose cryptographic
22 | library based on the code from GnuPG. It provides
23 | functions for all cryptographic building blocks:
24 | symmetric ciphers, hash algorithms, MACs, public
25 | key algorithms, large integer functions, random
26 | numbers and a lot of supporting functions.
27 | - [[file:libassuan/index.org][Libassuan]] :: Libassuan is the IPC library used by some GnuPG
28 | related software.
29 | - [[file:libksba/index.org][Libksba]] :: Libksba provides an easy API to create and parse
30 | X.509 and CMS related objects.
31 | - [[file:npth/index.org][nPth]] :: The New GNU Portable Threads Library.
32 |
33 |
34 | ** Libraries recommended for use with GnuPG
35 |
36 | These libraries are not required to build GnuPG but are recommended
37 | by the GnuPG Project.
38 |
39 | - [[file:gpgme/index.org][GPGME]] :: GnuPG Made Easy is a library designed to make access to
40 | GnuPG easier for applications.
41 |
42 | ** Other Libraries
43 |
44 | - [[file:ntbtls/index.org][ntbTLS]] :: The Not Too Bad TLS Library.
45 | - [[file:swlist.org::#gnupg-for-java][gnupg-for-java]] :: Java binding for GPGME
46 | - [[file:swlist.org::#egd][EGD]] :: Entropy Gathering Daemon
47 |
48 | # eof
49 |
--------------------------------------------------------------------------------
/misc/jenkins/bin/run-tests.bat:
--------------------------------------------------------------------------------
1 | @echo off
2 |
3 | set BIN_PREFIX=d:\gnupg
4 | set abs_top_srcdir=%BIN_PREFIX%
5 | set PATH=%BIN_PREFIX%;%PATH%
6 | set GPGSCM_PATH=%BIN_PREFIX%/tests/gpgscm;%BIN_PREFIX%/tests/openpgp
7 | set EXEEXT=.exe
8 | set TMP=c:\temp
9 | set WD=c:\temp\logs
10 | mkdir %TMP%
11 | mkdir %WD%
12 |
13 | cd /d %BIN_PREFIX%
14 | echo Running self tests...
15 | %BIN_PREFIX%\gpgscm.exe --verbose tests/gpgscm/t-child.scm
16 |
17 | rem the gpgtar.scm is acting up (looping), and we don't deal with that
18 | rem well atm, so we simply omit it
19 |
20 | echo Running OpenPGP tests...
21 | cd /d %WD%
22 | mkdir openpgp
23 | cd openpgp
24 |
25 | %BIN_PREFIX%\gpgscm.exe %abs_top_srcdir%/tests/openpgp/run-tests.scm --parallel version.scm enarmor.scm mds.scm decrypt.scm decrypt-multifile.scm decrypt-dsa.scm decrypt-session-key.scm sigs.scm sigs-dsa.scm encrypt.scm encrypt-multifile.scm encrypt-dsa.scm compression.scm seat.scm clearsig.scm encryptp.scm detach.scm detachm.scm armsigs.scm armencrypt.scm armencryptp.scm signencrypt.scm signencrypt-dsa.scm armsignencrypt.scm armdetach.scm armdetachm.scm genkey1024.scm conventional.scm conventional-mdc.scm multisig.scm verify.scm verify-multifile.scm gpgv-forged-keyring.scm armor.scm import.scm import-revocation-certificate.scm ecc.scm 4gb-packet.scm tofu.scm use-exact-key.scm default-key.scm export.scm ssh-import.scm ssh-export.scm quick-key-manipulation.scm key-selection.scm delete-keys.scm gpgconf.scm issue2015.scm issue2346.scm issue2417.scm issue2419.scm issue2929.scm
26 |
27 | echo Running gpgsm tests...
28 | cd /d %WD%
29 | mkdir gpgsm
30 | cd gpgsm
31 |
32 | set GPGSCM_PATH=%BIN_PREFIX%/tests/gpgscm;%BIN_PREFIX%/tests/openpgp;%BIN_PREFIX%/tests/gpgsm
33 | %BIN_PREFIX%\gpgscm.exe %abs_top_srcdir%/tests/gpgsm/run-tests.scm --parallel import.scm encrypt.scm verify.scm decrypt.scm sign.scm export.scm
34 |
35 | echo Running GPGME tests...
36 | cd /d %WD%
37 | mkdir gpgme
38 | cd gpgme
39 |
40 | rem set verbose=3
41 | set GPGSCM_PATH=%BIN_PREFIX%/tests/gpgscm;%BIN_PREFIX%/tests/openpgp;%BIN_PREFIX%/tests/gpgme
42 | set XTEST_GPGME_SRCDIR=%BIN_PREFIX%/gpgme
43 | set XTEST_GPGME_BUILDDIR=%BIN_PREFIX%/gpgme/obj.w32
44 | %BIN_PREFIX%\gpgscm.exe %abs_top_srcdir%/tests/gpgme/run-tests.scm --parallel
45 |
--------------------------------------------------------------------------------
/web/download/iconv.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - About iconv.dll
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 |
5 | * Installing iconv.dll
6 |
7 | To support different languages and character sets, Microsoft Windows
8 | versions of GnuPG make use of a DLL called “iconv.dll”. This DLL has
9 | been written by the GNU project too and is used by several
10 | applications ported from GNU/Linux to MS Windows systems. If this
11 | library has not yet been installed on your system, an error message
12 | might have you taken to this page. Please follow the instructions
13 | below to install this library.
14 |
15 | GnuPG has a fallback mechanism to work even without this DLL.
16 | However, some texts may not show up correclty and when creating a
17 | new key it might not be encoded correctly. Thus, unless you are
18 | using the Latin-1 or UTF-8 character set, you should definitley
19 | install the DLL before you create a new key or add a new user ID to
20 | a key.
21 |
22 | The DLL is available as a ZIP file at the address
23 | [[ftp://ftp.gnupg.org/gcrypt/binary/libiconv-1.9.1.dll.zip][ftp://ftp.gnupg.org/gcrypt/binary/libiconv-1.9.1.dll.zip]]. You
24 | should also get the [[ftp://ftp.gnupg.org/gcrypt/binary/libiconv-1.9.1.dll.zip.sig][corresponding ".sig" file]] and [[integrity_check.org][verify the
25 | integrity]]. This DLL has been built from the source package
26 | libiconv-1.9.1.tar.gz available at the same FTP sites. We
27 | distribute it separately for convenience and because GnuPG only
28 | requires this DLL and not the other files from the binary
29 | package. For copying conditions see the included file “COPYING.LIB”.
30 |
31 | If you used the [[http://www.gpg4win.org][Gpgwin]] package to install GnuPG, you should never
32 | see this message because this DLL will get installed. However, it
33 | might happen that such a DLL has been installed on your system by
34 | another application and later be deinstalled. To rectify this,
35 | simply re-install Gpg4win and your are done.
36 |
37 | Note that starting with GnuPG version 2.0.21, this external DLL is
38 | not anymore required.
39 |
40 | To install this DLL, unzip it and copy the file “iconv.dll” to a
41 | directory where you usually keep DLLs. If you don’t know such a
42 | directory, it is safe to copy it into the same directory as the
43 | "gpg.exe" file is stored.
44 |
--------------------------------------------------------------------------------
/web/documentation/security.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GnuPG - Security
2 | #+STARTUP: showall
3 | #+SETUPFILE: "../share/setup.inc"
4 |
5 | * Security
6 |
7 | The GnuPG Project takes the security of software it develops very
8 | seriously. In general we prefer a [[https://en.wikipedia.org/wiki/Full_disclosure_(computer_security)][full disclosure]] approach and all
9 | bugs listed in our [[file:bts.org][bug tracker]] as well as code changes in our [[../download/git.org][software
10 | repository]] are public. Given that GnuPG is an important part of many
11 | software distributions and severe bugs in GnuPG would affect their
12 | users directly, we co-ordinate with them in private as soon as we
13 | learn about a severe vulnerability.
14 |
15 | Sometimes we receive pre-notifications of research which may lead to a
16 | new kind of vulnerability. In these cases we may work with the
17 | researchers in private on a solution and co-ordinate our fix release
18 | with them.
19 |
20 |
21 | ** Threat Model of libgcrypt
22 |
23 | Libgcrypt has been developed for use in a wide variety of platforms
24 | with different security needs. Some platforms exhibit fine-grained
25 | side channels which can be used to spy on processes running in other
26 | containers or virtual machines. Although Libgcrypt implements many
27 | countermeasures against such side-channels attacks, it is not possible
28 | to avoid all of them. In the worst case it is thus possible to leak
29 | the entire private key or a password to a malicious process running in
30 | another virtual machine on the same hardware.
31 |
32 | Those hardware related threats are out of scope in Libgcrypt's threat
33 | model. It is up to users not to offer any access to those
34 | side-channels.
35 |
36 |
37 | ** Security contact
38 |
39 | If you found a *severe* security problem and you do not want to
40 | publish it, please report it by mail to security at gnupg.org. We
41 | prefer reports in plain text format; if needed we can also work with
42 | PDF files. For security reasons we won't read any other complex data
43 | formats (e.g. docx or odt).
44 |
45 | Note that we do not use a team OpenPGP key. Thus please write a
46 | non-encrypted message to the security address and ask for the keys of
47 | the developers at duty and then encrypt the mail to all of them. A
48 | list of our core developers can be found [[../people/index.org][here]]; they are all active on
49 | the gnupg-devel mailing list.
50 |
--------------------------------------------------------------------------------
/web/faq/gpgme-faq.org:
--------------------------------------------------------------------------------
1 | #+TITLE: GPGME FAQ --- GnuPG.org
2 |
3 | * GPGME FAQ
4 |
5 | GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG
6 | easier for applications. It provides a High-Level Crypto API for
7 | encryption, decryption, signing, signature verification and key
8 | management.
9 |
10 |
11 |
12 | * Frequently Asked Questions
13 |
14 | ** Why does the function =gpgme_data_seek= not work?
15 |
16 | You probably did not compile the program with largefile support. GPGME
17 | is compiled with largefile support by default, so off_t is a 64-bit
18 | data type. Because =gpgme_data_seek= uses =off_t= as a parameter type, you
19 | have to compile your program with largefile support as well, so that
20 | the data types used by GPGME and by your program match.
21 |
22 | Note that you have to compile your program with largefile support even
23 | if you do not use =gpgme_data_seek=, because file descriptors are
24 | exchanged between the program and GPGME.
25 |
26 | The GPGME documentation contains much more information on the subject.
27 | See section 2.3 Largefile support of the GPGME Reference Manual.
28 |
29 |
30 | ** Why don't the Python bindings announced in 2016 work?
31 |
32 | The Python bindings have been undergoing continual improvement and
33 | fine tuning since the initial announcement. To obtain the most
34 | accurate bindings it is recommended to install the bindings shipped
35 | with GPGME itself rather than older versions available on PyPI.
36 |
37 | The Python module has been renamed from =pyme= or =pyme3= and is
38 | now simply called =gpg=. Otherwise the function remains similar
39 | and example code is included with the source.
40 |
41 | A basic decryption operation to take an encrypted file and decrypt
42 | it with a key in your secret keys would look something like this:
43 |
44 | #+begin_example
45 | import gpg
46 |
47 | ciphertext = open("filename.txt.asc", "rb")
48 | plaintext = gpg.Context().decrypt(ciphertext)
49 | ciphertext.close()
50 | f = open("filename.txt", "wb")
51 | f.write(plaintext[0])
52 | f.close()
53 | del plaintext
54 | #+end_example
55 |
56 |
57 |
58 |
59 | # Copyright (C) 2002-2004 Free Software Foundation, Inc.
60 | # Copyright (C) 2006-2018 The GnuPG Project.
61 | #
62 | # Written by Werner Koch (2006-04-27 12:50:00).
63 | # Ammended by Ben McGinnes (2018-02-14 08:21:32 UTC).
64 |
--------------------------------------------------------------------------------
/misc/id/openpgp-webkey-service/Makefile:
--------------------------------------------------------------------------------
1 | # Makefile for the OpenPGP Web Key Directory I-D
2 | #
3 | # Prerequisites: apt install ruby-kramdown-rfc2629 xml2rfc
4 | #
5 | # For pdf output, also: apt install weasyprint
6 |
7 | draft = draft
8 | OUTPUT = $(draft).txt $(draft).html $(draft).xml
9 |
10 | all: $(OUTPUT)
11 |
12 | %.xmlv2: %.md
13 | kramdown-rfc2629 < $< > $@.tmp
14 | mv $@.tmp $@
15 |
16 | # convert to v3:
17 | %.xml: %.xmlv2
18 | xml2rfc -o $@ --v2v3 $<
19 |
20 | %.html: %.xml
21 | xml2rfc $< --html
22 |
23 | %.txt: %.xml
24 | xml2rfc $< --text
25 |
26 | %.pdf: %.xml
27 | xml2rfc $< --pdf
28 |
29 | $(draft).txt.diff: $(draft).txt compare canonicalizetxt
30 | ! ./compare > $@.tmp
31 | mv $@.tmp $@
32 |
33 | clean:
34 | -rm -rf $(OUTPUT) $(draft).xmlv2 $(draft).txt.diff
35 |
36 | .PHONY: clean all
37 | .SECONDARY: $(draft).xmlv2
38 |
39 |
40 | # Old stuff when we generated the .md from .org
41 | #
42 | # MD_EXAMPLE_FIX = '(defun org-md-example-block (example-block contents info) \
43 | # "with fixed indentation" \
44 | # (replace-regexp-in-string \
45 | # "^" " " \
46 | # (org-remove-indentation \
47 | # (org-export-format-code-default example-block info))))'
48 | #
49 | #
50 | # # Take care:
51 | # # You may need to modify pandoc2rfc so that is used
52 | # # -t docbook4
53 | # # because the "-t docbook" seems to be mapped to "-t docbook5" by
54 | # # current pandoc versions. Also the quote tag needs to be replaced
55 | # # by adding
56 | # # sed -e 's,,",g' -e 's,,",g'
57 | # # to the output of docbook.
58 | #
59 | # draft.txt, draft.xml: draft.org
60 | # emacs --batch \
61 | # --eval "(require 'org)" \
62 | # --eval "(require 'ox-md)" \
63 | # --eval $(MD_EXAMPLE_FIX) \
64 | # --visit "draft.org" \
65 | # --eval "(org-md-export-to-markdown)"
66 | # sed -i 's/\*\*\(.*\):\*\*/"\1":/' draft.md
67 | # sed template.xml
68 | # sed tmp-abstract.md
70 | # sed tmp-middle.md
72 | # sed tmp-back.md
74 | # : pandoc2rfc tmp-abstract.md tmp-middle.md tmp-back.md
75 | # : pandoc2rfc -X tmp-abstract.md tmp-middle.md tmp-back.md
76 | # : rm template.xml tmp-abstract.md tmp-middle.md tmp-back.md draft.md
77 | #
78 |
--------------------------------------------------------------------------------
/misc/howtos.gnupg.org/en/GPGMiniHowto-4.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Gnu Privacy Guard (GnuPG) Mini Howto (English): Encrypt and decrypt
6 |
7 |
8 |
9 |
10 |
11 | Next
12 | Previous
13 | Contents
14 |
15 |
After installing everything and configuring everything in the way we want,
17 | we can start on encrypting and decrypting.
18 |
When encrypting or decrypting it is possible to have more than one private key
19 | in use. If this occurs you need to select the active key. This can be done by
20 | using the option -u UID or by using the option --local-user UID.
21 | This causes the default key to use to be replaced by wanted key.
22 |
If you want to change recipient this can be done by the option -r
23 | or by the option --recipient.
55 | Also here stdout is preset, but with the -o option you can
56 | redirect the output to a file.
57 |
58 | Next
59 | Previous
60 | Contents
61 |
62 |
63 |
--------------------------------------------------------------------------------
/misc/blog.gnupg.org/20131113-friends-tell-friends-they-love-gnupg.org:
--------------------------------------------------------------------------------
1 | # Old blog post converted from HTML to ORG.
2 | #+STARTUP: showall
3 | #+AUTHOR: Sam Tuke
4 | #+DATE: 13th November 2013
5 |
6 | ** Friends tell friends they love GnuPG
7 |
8 | #+CAPTION: GnuPG can run almost anywhere
9 | #+ATTR_HTML: :class right
10 | [[file:img/android.jpg]]
11 |
12 | Email encryption is one of those pleasures that can't be enjoyed alone.
13 | Sending yourself messages secured with 4096-bit RSA is great for proof
14 | of concept, but meaningful communication requires two parties. GnuPG
15 | requires both those parties to have their own keys.
16 |
17 | Less than 1% of all email traffic is PGP encrypted, meaning that those
18 | of us who do make our messages private routinely find ourselves in the
19 | frustrating predicament of having to share our thoughts insecurely, even
20 | though we know they're being intercepted, even though this is easily
21 | avoidable, and even though we've already taken steps to do so. All
22 | because our *friends and colleagues* don't know the benefits of GnuPG.
23 |
24 | Windows, Gnu/Linux, Mac, and Android all have point and click GnuPG
25 | interfaces - at this point, all bases except iPhone are more or less
26 | covered. That means the reason your contacts aren't OpenPGP ready is
27 | *not technical*. And because GnuPG is Free Software (and free of
28 | charge), it can't be about price.
29 |
30 | A recommendation from you is the most effective way you can increase the
31 | number of GnuPG users, and consequently increase the percentage of the
32 | messages you send that are meaningfully encrypted. That's why we're
33 | asking people in our community to think of pithy explanations of why
34 | GnuPG is important and how it enables them.
35 |
36 | We've already got quotes from some big names like Bruce Schneier, Jacob
37 | Appelbaum, and Richard Stallman. But the chances are that *your name*
38 | carries more weight among your peers. Please use it to share your
39 | appreciation for GnuPG!
40 |
41 | If you use social networks, you can use [[https://twitter.com/search?q=%23ilovegpg][#iloveGPG]] to connect your
42 | messages to other people's, and make is easier for us to find and
43 | repeat them.
44 |
45 | Look out for weekly quotes posted from the GnuPG [[https://twitter.com/gnupg][Twitter]] and [[https://www.cryptospora.net/u/gnuprivacyguard][Diaspora]]
46 | accounts if you need inspiration. Let's fill up the [[http://keys.gnupg.net/][keyservers]] with
47 | fresh keys from new users!
48 |
--------------------------------------------------------------------------------
/misc/howtos.gnupg.org/card-howto/en/css/smartcard.css:
--------------------------------------------------------------------------------
1 | /* Adjust docbook areas */
2 |
3 | div.note span.important {
4 | color: black;
5 | background-color : red;
6 | font-weight: bold;
7 | font-size: 12pt;
8 | }
9 |
10 | /* Adjust docbook
To sign data with your own key, use the command:
17 |
18 |
19 | gpg -s (or --sign) [Data]
20 |
21 |
22 | By doing this also compression takes place. This means that the result is not
23 | legible. If you want a legible result you can use:
24 |
25 |
26 |
27 | gpg --clearsign [Data]
28 |
29 |
30 | this will make sure that the results are clearly legible. Furthermore it does
31 | the same (signing data).
32 |
With
33 |
34 |
35 | gpg -b (or --detach-sign) [Data]
36 |
37 |
38 | you can write the signature in a separate file. It is highly recommended to use
39 | this option especially when signing binary files (like archives for instance).
40 | Also the --armor option can be extremely useful here.
41 |
Quite often you find that data is encrypted and signed as well. The full
42 | instruction looks like:
43 |
The functionality of the options -u (--local-user) and -r
50 | (--recipient) are as described before.
51 |
When encrypted data has been signed as well, the signature is checked when the
52 | data is decrypted. You can check the signature of signed data by using the command:
53 |
54 |
55 | gpg [--verify] [Data]
56 |
57 |
58 | This will only work (of course) when you own the public key of the sender.
59 |
60 | Next
61 | Previous
62 | Contents
63 |
64 |
65 |
--------------------------------------------------------------------------------