diff --git a/misc/id/openpgp-webkey-service/draft.org b/misc/id/openpgp-webkey-service/draft.org
index 7d3c740..a57ddfc 100644
--- a/misc/id/openpgp-webkey-service/draft.org
+++ b/misc/id/openpgp-webkey-service/draft.org
@@ -1,724 +1,729 @@
# openpgp-webkey-service
#+startup: showall
#+options: toc:nil
#+macro: RFC [](#RFC$1)
#+macro: https_scheme ~https://~
#+begin_src rfc
]>
OpenPGP Web Key Directory
GnuPG e.V.
wk@gnupg.org
https://gnupg.org/verein
Security
&pandocAbstract;
&pandocMiddle;
&rfc.2119;
&rfc.2782;
&rfc.3156;
&rfc.4880;
&rfc.5785;
&rfc.6189;
&pandocBack;
#+end_src
* Abstract
This specification describes a service to locate OpenPGP keys by mail
address using a Web service and the HTTPS protocol. It also provides a
method for secure communication between the key owner and the mail
provider to publish and revoke the public key.
* Middle
* Introduction
This memo describes a method to associate OpenPGP keys with a mail
address and how to look them up using a web service with a well-known
URI. In addition a mail based protocol is given to allow a client to
setup such an association and to maintain it.
* Notational Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in {{{RFC(2119)}}}.
* Web Key Directory
A major use case for OpenPGP is the encryption of mail. A common
difficulty of sending encrypted mails to a new communication partner is
to find the appropriate public key of the recipient. Unless an
off-channel key exchange has been done, there are no easy ways to
discover the required key. The common practice is to search the network
of public key servers for a key matching the recipient's mail address.
This practise bears the problem that the keyservers are not able to give
a positive confirmation that a key actually belongs to the mail
addresses given in the key. Further, there are often several keys
matching a mail address and thus one needs to pick a key on good luck.
This is clearly not a secure way to setup an end-to-end encryption. Even
if the need for a trusted key for an initial mail message is
relinquished, a non-authenticated key may be a wrong one and the actual
recipient would receive a mail which she can't decrypt, due to the use
of a wrong key.
Methods to overcome this problem are
- sending an initial unencrypted message with the public key attached,
- using the OpenPGP DANE protocol to lookup the recipients key via the
DNS.
The first method has the obvious problems of not even trying to encrypt
the initial mail, an extra mail round-trip, and problems with unattended
key discovery.
The latter method works fine but requires that mail providers need to
set up a separate DNS resolver to provide the key. The administration of
a DNS zone is often not in the hands of small mail installations. Thus
an update of the DNS resource records needs to be delegated to the ISP
running the DNS service. Further, DNS lookups are not encrypted and
missing all confidentially. Even if the participating MUAs are using
STARTTLS to encrypt the mail exchange, a DNS lookup for the key
unnecessarily identifies the local-part of the recipients mail address
to any passive eavesdroppers.
This memo specified a new method for key discovery using an encrypted
https connection.
** Key Discovery
Although URIs are able to encode all kind of characters, straightforward
implementations of a key directory may want to store the local-part of
a mail address directly in the file system. This forbids the use of
certain characters in the local-part. To allow for such an
implementation method the URI uses an encoded form of the local-part
which can be directly mapped to a file name.
OpenPGP defines its User IDs, and thus the mail address, as UTF-8
strings. To help with the common pattern of using capitalized names
(e.g. "Joe.Doe@example.org") for mail addresses, and under the premise
that almost all MTAs treat the local-part case-insensitive and that
the domain-part is required to be compared case-insensitive anyway,
all upper-case ASCII characters in a User ID are mapped to lowercase.
Non-ASCII characters are not changed.
The so mapped local-part is hashed using the SHA-1 algorithm. The
resulting 160 bit digest is encoded using the Z-Base-32 method as
described in {{{RFC(6189)}}}, section 5.1.6. The resulting string has
a fixed length of 32 octets. To form the URI, the following parts are
concatenated:
- The scheme {{{https_scheme}}},
- the domain-part,
- the string ~/.well-known/openpgpkey/hu/~,
- and the above constructed 32 octet string.
For example the URI to lookup the key for Joe.Doe@Example.ORG is:
#+BEGIN_EXAMPLE
https://example.org/.well-known/openpgpkey/
hu/iy9q119eutrkn8s1mk4r39qejnbu3n5q
#+END_EXAMPLE
(line has been wrapped for rendering purposes)
DNS SRV resource records ({{{RFC(2782)}}}) may be used to query a
different host or a port other than 443. For example:
#+BEGIN_EXAMPLE
_openpgpkey._tcp.example.org. IN SRV 0 0 8443 wkd.example.org.
#+END_EXAMPLE
changes the above to query the host "wkd.example.org" at port
8443 instead of the host "example.org" at port 443. The target (in the
example "wkd.example.org") MUST be a sub-domain of the domain-part
(here "example.org"). If the target is not a sub-domain, the SRV RR
MUST be be ignored. The recommended name for the sub-domain is "wkd".
The HTTP GET method MUST return the binary representation of the
OpenPGP key for the given mail address. The key needs to carry a User
ID packet ({{{RFC(4880)}}}) with that mail address. Note that the key
may be revoked or expired - it is up to the client to handle such
conditions. To ease distribution of revoked keys, a server may return
revoked keys in addition to a new key. The keys are returned by a
single request as concatenated key blocks.
The server MUST accept the HTTP HEAD method to allow a client to
check for the existence of a key.
The server SHOULD use "application/octet-string" as the
Content-Type for the data but clients SHOULD also accept any other
Content-Type. The server MUST NOT return an ASCII armored version of
the key.
The server MUST serve a Policy Flags file as specified below. That
file is even required if the Web Key Directory Update Protocol is not
supported.
* Web Key Directory Update Protocol
To put keys into the key directory a protocol to automate the task is
desirable. The protocol defined here is entirely based on mail and
the assumption that a mail provider can securely deliver mail to the
INBOX of a user (e.g. an IMAP folder). Note that the same protocol
may also be used for submitting keys for use with OpenPGP DANE.
We assume that the user already created a key for her mail account
alice@example.org. To install the key at her provider's Web Key
Directory, she performs the following steps:
1. She retrieves a file which contains one line with the mail address
used to submit the key to the mail provider. The DNS SRV rules
described for the Web Key Directory apply here as well. See below
for the syntax of that file. For a mail address at the domain
"example.org" the URI of the file is
#+begin_example
https://example.org/.well-known/openpgpkey/submission-address
#+end_example
2. She sends her key using SMTP (or any other transport mechanism) to
the provider using the submission address and key format as specified
by PGP/MIME.
3. The provider checks that the received key has a User ID which matches
an account name of the provider.
4. The provider sends an encrypted message containing a nonce and the
fingerprint of the key to the mail account of the user. Note that a
similar scheme is used by the well known caff(1) tool to help with
key signing parties.
5. A legitimate user will be able to decrypt the message because she
created the key and is in charge of the private key. This step
verifies that the submitted key has actually been created by the
owner of the account.
6. The user sends the decrypted nonce back to the submission address
as a confirmation that the private key is owned by her and that the
provider may now publish the key. Although technically not
required, it is suggested that the mail to the provider is
encrypted. The public key for this is retrieved using the key
lookup protocol described above.
7. The provider receives the nonce, matches it with its database of
pending confirmations and then publishes the key. Finally the
provider sends a mail back to the user to notify her of the
publication of her key.
The message data structures used for the above protocol are specified in
detail below. In the following sections the string "WELLKNOWN" denotes
the first part of an URI specific for a domain. In the examples the
domain "example.org" is assumed, thus
#+BEGIN_EXAMPLE
WELLKNOWN := https://example.org/.well-known/openpgpkey
#+END_EXAMPLE
The term "target key" denotes the to be published key, the term
"submission key" the key associated with the submission-address of the
mail provider.
** The Submission Address
The address of the submission file is
#+BEGIN_EXAMPLE
WELLKNOWN/submission-address
#+END_EXAMPLE
The file consists of exactly one line, terminated by a LF, or the
sequence of CR and LF, with the full mail address to be used for
submission of a key to the mail provider. For example the content of the
file may be
#+BEGIN_EXAMPLE
key-submission-example.org@directory.example.org
#+END_EXAMPLE
** The Submission Mail
The mail used to submit a key to the mail provider MUST comply to the
PGP/MIME specification ({{{RFC(3156)}}}, section 7), which states that
the Content-Type must be "application/pgp-keys", there are no required
or optional parameters, and the body part contains the ASCII-armored
transferable Public Key Packets as defined in {{{RFC(4880)}}}, section
11.1.
The mail provider MUST publish a key capable of signing and encryption
for the submission-address in the Web Key Directory or via DANE. The
key to be published MUST be submitted using a PGP/MIME encrypted
message ({{{RFC(3156)}}}, section 4). The message MUST NOT be signed
(because the authenticity of the signing key has not yet been
confirmed). After decryption of the message at the mail provider a
single "application/pgp-keys" part, as specified above, is expected.
** The Confirmation Request
The mail provider sends a confirmation mail in response to a received
key publication request. The message MUST be sent from the
submission-address of the mail provider to the mail address extracted
from the target key. The message needs to be a PGP/MIME signed
message using the submission key of the provider for the
signature. The signed message MUST have two parts:
The first part MUST have "text" as its Content-Type and can be used to
explain the purpose of the mail. For example it may point to this RFC
and explain on how to manually perform the protocol.
The second part MUST have "application/vnd.gnupg.wkd" if the protocol
version of the server is 5 or later; without a known protocol version
or a version less than 5, "application/vnd.gnupg.wks" MUST be used as its
Content-Type and carry an OpenPGP encrypted message in ASCII Armor
format. The message MUST be encrypted to the target key and MUST NOT
be signed. After decryption a text file in the Web Key data format
must be yielded.
That data format consists of name-value pairs with one name-value pair
per LF or CR+LF terminated line. Empty lines are allowed and will be
ignored by the receiver. A colon is used to terminate a name.
In a confirmation request the following names MUST be send in the
specified order:
- type :: The value must be "confirmation-request".
- sender :: This is the mailbox the user is expected to sent the
confirmation response to. The value must match the
mailbox part of the "From:" address of this
request. Exactly one address MUST be given.
- address :: The value is the addr-spec part of the target key's
mail address. The value SHOULD match the addr-spec part
of the recipient's address. The value MUST be UTF-8
encoded as required for an OpenPGP User ID.
- fingerprint :: The value is the fingerprint of the target key. The
fingerprint is given in uppercase hex encoding
without any interleaving spaces.
- nonce :: The value is a string with a minimum length of 16 octets
and a maximum length of 64 octets. The string must
entirely be made up of random ASCII letters or
digits. This nonce will be sent back to the mail provider
as proof that the recipient is the legitimate owner of
the target-key.
The receiver of that message is expected to verify the outer signature
and disregard the entire message if it can't be verified or has not
been signed by the key associated with the submission address.
After the message as been verified the receiver decrypts the second part
of the message, checks that the "fingerprint" matches the target key,
checks that the "address" matches a User ID of the target key, and
checks the other constrains of the request format. If any constraint
is not asserted, or the fingerprint or User ID do not match the target
key, or there is no pending publication requests (i.e. a mail recently
sent o the submission address), the user MAY be notified about this
fake confirmation attempt.
In other cases the confirmation request is legitimate and the MUA
shall silently send a response as described in the next section.
The rationale for the outer signature used with this request is to
allow early detection of spam mails. This can be done prior to the
decryption step and avoids asking the user to enter a passphrase to
perform the decryption for a non-legitimate message. The use of a
simple encrypted attachment, instead of using PGP/MIME encryption, is
to convey the Content-Type of that attachment in the clear and also to
prevent automatic decryption of that attachment by PGP/MIME aware
clients. The MUA may in fact detect this confirmation request and
present a customized dialog for confirming that request.
** The Confirmation Response
A response to a confirmation request MUST only be send in the positive
case; there is no negative confirmation response. A mail service
provider is expected to cancel a pending key submission after a suitable
time without a confirmation. The mail service provider SHOULD NOT retry
the sending of a confirmation request after the first request has been
send successfully.
The user MUST send the confirmation response from her target mail
address to the "from" address of the confirmation request. The
message MUST be signed and encrypted using the PGP/MIME Combined
format ({{{RFC(3156)}}}, section 6.2). The signing key is the target
key and the encryption key is the key associated with the provider's
submission address.
The Content-Type used for the plaintext message MUST match the
Content-Type of the request. The format is the same as described
above for the Confirmation Request. The body must contain three
name-value pairs in this order:
- type :: The value must be "confirmation-response".
- sender :: The value must match the mailbox part of the "From:"
address of this response. Exactly one address MUST be
given.
- nonce :: The value is the value of the "nonce" parameter from the
confirmation request.
** Policy Flags
For key generation and submission it is useful to tell the
client about certain properties of the mail provider in advance. This
can be done with a file at the URL
#+BEGIN_EXAMPLE
WELLKNOWN/policy
#+END_EXAMPLE
A site supporting the Web Key Directory MUST serve this file; it is
sufficient if that file has a zero length. Clients may use this file
to check for Web Key Directory support.
The file contains keywords and optionally values, one per line with
each line terminated by a LF or the sequence of CR and LF. Empty lines
and lines starting with a '#' character are considered comment
lines. A keyword is made up of lowercase letters, digits, hyphens, or
dots. An underscore is allowed as a name space delimiters; see
below. The first character must be a letter. Keywords which are
defined to require a value are directly followed by a colon and then
after optional white space the value. Clients MUST use
case-insensitive matching for the keyword.
Currently defined keywords are:
- mailbox-only :: The mail server provider does only accept keys
with only a mailbox in the User ID. In particular
User IDs with a real name in addition to the
mailbox will be rejected as invalid.
- dane-only :: The mail server provider does not run a Web Key
Directory but only an OpenPGP DANE service. The Web
Key Directory Update protocol is used to update the
keys for the DANE service.
- auth-submit :: The submission of the mail to the server is done
using an authenticated connection. Thus the
submitted key will be published immediately without
any confirmation request.
- protocol-version :: This keyword can be used to explicitly claim the
support of a specific version of the Web Key Directory update protocol.
This is in general not needed but implementations may have
workarounds for providers which only support an old protocol
version. If these providers update to a newer version they
should add this keyword so that the implementation can disable
the workaround. The value is an integer corresponding to the
respective draft revision number.
+- submission-address :: An alternative way to specify the submission
+ address. The value is the addr-spec part of the address to send
+ requests to this server. If this keyword is used in addition to
+ the =submission-address= file, both MUST have the same value.
+
# Fixme: Add a protocol-version value for the final RFC.
More keywords will be defined in updates to this I-D. There is no
registry except for this document. For experimental use of new
features or for provider specific settings, keywords MUST be prefixed
with a domain name and an underscore.
* Security Considerations
The use of SHA-1 for the mapping of the local-part to a fixed string
is not a security feature but merely used to map the local-part to a
fixed-sized string made from a well defined set of characters. It is not
intended to conceal information about a mail address.
The domain name part of the mail address is not part of the hash to
avoid problems with internationalized domain names. Instead a
separate URL is required for each domain name.
The use of DNS SRV records reduces the certainty that a mail address
belongs to a domain. For example an attacker may change the target to
a host in a sub-domain under their control and thus gain full control
over all keys. An implementation may want to weight the certainty of
a mapping different if it has been retrieved via a sub-domain and in
particular if a non-recommended name is used for the sub-domain.
To make it a bit harder to test for published keys, the server
responsible to serve the WELLKNOWN directory SHOULD NOT create an
index file for that directory or any sub-directory.
* IANA Considerations
** Well-Known URI
IANA is requested to assign a well-known URI in the "Well-Known URIs"
registry as defined by {{{RFC(5785)}}}:
URI suffix: openpgpkey
Change controller: IETF
Specification document: This
* Acknowledgments
The author would like to acknowledge the help of the individuals who
kindly voiced their opinions on the GnuPG mailing lists, in particular,
the help of Bernhard Reiter and Guilhem Moulin.
* Back
* Sample Protocol Run
The following non-normative example can be used by implementors as
guidance.
Note that GnuPG version 2.1.12 supports the key discovery described in
version -00 of this document (auto-key-locate method "wkd"). Version
2.1.16 can run the protocol described in this document but is also able
to run the protocol version specified by -01. For backward
compatibility this example uses the Content-Type as required for
versions of this protocol prior to -04; if the client knows that the
server support -04 "vnd.gnupg.wkd" should be used.
** Sample Keys
This is the provider's submission key:
#+begin_example
-----BEGIN PGP PRIVATE KEY BLOCK-----
lFgEV/TAohYJKwYBBAHaRw8BAQdAB/k9YQfSTI8qQqqK1KimH/BsvzsowWItSQPT
FP+fOC4AAP46uJ3Snno3Vy+kORye3rf0VvWvuz82voEQLxG6WpfHhREEtBprZXkt
c3VibWlzc2lvbkBleGFtcGxlLm5ldIh5BBMWCAAhBQJX9MCiAhsDBQsJCAcCBhUI
CQoLAgQWAgMBAh4BAheAAAoJEKhtNooW0cqEWMUA/0e9XaeptszWC9ZvPg8INL6a
BvRqPBYGU7PGmuXsxBovAQDyckOykG0UAfHVyN1w4gSK/biMcnqVr857i8/HuvjW
C5xdBFf0wKISCisGAQQBl1UBBQEBB0Apvaoe4MtSEJ1fpds/4DFl2kXXBpnVji/s
Wg9btdthNQMBCAcAAP9FJX99T1LEJzBnvBBnc6bimnT6/1OKM9RdO4R0/uVP6BFL
iGEEGBYIAAkFAlf0wKICGwwACgkQqG02ihbRyoTlGwD9FBr92osjL7HkhhZZ7Z2D
My3b9zpoZeMjvPg5YPqpdKMA/jhZoHuZCRMBYf7YRFb8aXtuyetDFZYrkjnum+OG
HFAD
=Hnwd
-----END PGP PRIVATE KEY BLOCK-----
#+end_example
This is the target key to be published:
#+begin_example
-----BEGIN PGP PRIVATE KEY BLOCK-----
lFgEV2o9XRYJKwYBBAHaRw8BAQdAZ8zkuQDL9x7rcvvoo6s3iEF1j88Dknd9nZhL
nTEoBRkAAP94nCZMM4WY2IORXfM6phLGSz3RsHvs/vA1Opaus4+R3BKJtBtwYXRy
aWNlLmx1bXVtYmFAZXhhbXBsZS5uZXSIeQQTFggAIQUCV2o9XQIbAwULCQgHAgYV
CAkKCwIEFgIDAQIeAQIXgAAKCRATlWNoKgINCpkNAQDFDcwJUzsxu7aJUiPdpYXj
4uVarrXakxEE8mGFotWhLAD9GH4rqLDYIE3NKEU0s+Okt4tEIwJaV8H1NNPPPMiK
3g2cXQRXaj2NEgorBgEEAZdVAQUBAQdAFnnmZc99TuKk5iCq9wmYZUVF2RcXN2Cs
qAl8iGQQUWsDAQgHAAD/VN/VGmlcwGBPcLTya2hfU4t37nMcFCKdNSXjJ5DFA0AP
PohhBBgWCAAJBQJXaj2NAhsMAAoJEBOVY2gqAg0Ky4UA/0GmVaXzXemLvv1Xw4yx
Eaz/KfKKGc4RJ+38fyqUzw8NAQCohQ+ki3I5f84EXLZEiUiLsnVtOn1HNxvND/gW
TiFZBA==
=GHi7
-----END PGP PRIVATE KEY BLOCK-----
#+end_example
** Sample Messages
The first message triggeres the publication requests.
#+begin_example
From: patrice.lumumba@example.net
To: key-submission@example.net
Subject: Key publishing request
MIME-Version: 1.0
Content-Type: multipart/encrypted;
protocol="application/pgp-encrypted";
boundary="=-=01-e8k41e11ob31eefa36wo=-="
Date: Wed, 05 Oct 2016 10:15:51 +0000
--=-=01-e8k41e11ob31eefa36wo=-=
Content-Type: application/pgp-encrypted
Version: 1
--=-=01-e8k41e11ob31eefa36wo=-=
Content-Type: application/octet-stream
-----BEGIN PGP MESSAGE-----
hF4DUgLY5tvmW2sSAQdAR1AcqvFpQe/fHRZbf0xcnl9Tb+AtwaX2yZnZXGELGHsw
1/e3E0JptwM5tpRAVe71ooF8Zq4jl76ZgQKfj/SyjpLJxyoEDy2N5wTQaqW4JtML
0ukB1vh7dIRDxBJX/LQIJC0wz8o1Q3vjcLJKFFvDb7YrerABpPIzwOAupcgIbQHj
5m1+2WU5CL8ffyJy2h1jV2X4OnvWF1Sn6J6SVD6DfZpOPRt9TxSemJrN1LJ3lG0N
ts8AuYmCOeC1H2r5TYyxqkC98JF8+Nvyxd/fwne8IOjK9uixkNMC5H9/ZOH0YWCb
wBnNB4iXuym4OIPxiLkDymsVF0ww/XrODE9Y259EGmO45VFNrJAX3HFs9/PcMCVk
n2qMyEkr8LHiXeEPun6Z54RHUPYv2cUkEZ0hhSJ+rtBxkc/5D/cAScCEXRKFSKEF
jLJAvLK/u/ga5DAzVai+vh6b6Bq+YVPaD9GWMhWj4CgR90p9LULi6S/Hzwhv9Wzf
8fJoJOaDjyvRDgr09jYLWamxkS9NWxqwy6MXJvxwbNdd5XtqiW4Y4o0Ll1hDJhxR
ljn/XvotXKwhKN+4QGhIXDVt4Dl4XxS5ptWfVTau8W8DYqDsU2obEcfsirZv53M1
Q9FCD8CD9+dkBt8VAJekCWVhEltcRHxlrznbk2jxm93xSD2o6gZ5X0VSaSUXyEhm
J+8F3gyTHGgbq/TgyjFoockWh5EtGgAFuWvmPJCF5PO/UaNeoKwgwSJBu6oTXkHx
R4nvvMRcj5UgTsKpZ79NiDQukbjG5ScNT5TCUiiZsBXBqBx3fD61EH6cAuh4P3Kr
iM7PY4fwAHo890Dx+Qlt
=WIhx
-----END PGP MESSAGE-----
--=-=01-e8k41e11ob31eefa36wo=-=--
#+end_example
The server decrypts this message to
#+begin_example
Content-Type: application/pgp-keys
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEV2o9XRYJKwYBBAHaRw8BAQdAZ8zkuQDL9x7rcvvoo6s3iEF1j88Dknd9nZhL
nTEoBRm0G3BhdHJpY2UubHVtdW1iYUBleGFtcGxlLm5ldIh5BBMWCAAhBQJXaj1d
AhsDBQsJCAcCBhUICQoLAgQWAgMBAh4BAheAAAoJEBOVY2gqAg0KmQ0BAMUNzAlT
OzG7tolSI92lhePi5VqutdqTEQTyYYWi1aEsAP0YfiuosNggTc0oRTSz46S3i0Qj
AlpXwfU00888yIreDbg4BFdqPY0SCisGAQQBl1UBBQEBB0AWeeZlz31O4qTmIKr3
CZhlRUXZFxc3YKyoCXyIZBBRawMBCAeIYQQYFggACQUCV2o9jQIbDAAKCRATlWNo
KgINCsuFAP9BplWl813pi779V8OMsRGs/ynyihnOESft/H8qlM8PDQEAqIUPpIty
OX/OBFy2RIlIi7J1bTp9RzcbzQ/4Fk4hWQQ=
=qRfF
-----END PGP PUBLIC KEY BLOCK-----
#+end_example
and returns this confirmation request
#+begin_example
From: key-submission@example.net
To: patrice.lumumba@example.net
Subject: Confirm your key publication
MIME-Version: 1.0
Content-Type: multipart/encrypted;
protocol="application/pgp-encrypted";
boundary="=-=01-wrzqued738dfx4x97u7y=-="
Date: Wed, 05 Oct 2016 10:16:57 +0000
--=-=01-wrzqued738dfx4x97u7y=-=
Content-Type: application/pgp-encrypted
Version: 1
--=-=01-wrzqued738dfx4x97u7y=-=
Content-Type: application/octet-stream
-----BEGIN PGP MESSAGE-----
hF4DkYWHjk/NdMASAQdAluQeqhECpU2T0zEyBAEbFzhLkpubN160wjkFCrtUc0Mw
FwYgM2fp9cvTMdJ/xjkvmAcIEOT4AY/hn1yFQ4z0KG0gCkSac+8mkDylnPdxlXYw
0sBSAXlbqpVA7eUpFuU2Zs10zbIXxlwe6osR5wUIJut/RCOsYQmfvxC55x8mUX5/
zgTnNzlMzye5ws4pTgAeQm2x0Yv018L8IZgY5KxwJLBzlss0wLZ45ZcS80hR11Fx
NCow1fKF8lMnOJxagTEOih807nctz8vT5bR1gx0d7N3LM+th8nAg9/6Ghf1XTpLo
MzwGW0FtOG7Dg1Uxbw2bjaOuRBeh6IIpmNAw1pmIfnNu7PpoRydU5w1K/R8MT06z
MKdJ7IW5mVGes9EGnG3e4mjuILvNaZhfYy+a73IhDSaPm3oqdl1Qx7tbNg6lGjn6
KStCYAcPGPp3m7aWkfsPGThOVRhEXqaFFywfwSVEj1pdIRjDFA==
=Cdjh
-----END PGP MESSAGE-----
--=-=01-wrzqued738dfx4x97u7y=-=--
#+end_example
The client decrypts the attachment as
#+begin_example
Content-Type: application/vnd.gnupg.wks
Content-Transfer-Encoding: 8bit
type: confirmation-request
sender: key-submission@example.net
address: patrice.lumumba@example.net
fingerprint: B21DEAB4F875FB3DA42F1D1D139563682A020D0A
nonce: f5pscz57zj6fk11wekk8gx4cmrb659a7
#+end_example
creates this response
#+begin_example
Content-Type: application/vnd.gnupg.wks
Content-Transfer-Encoding: 8bit
type: confirmation-response
sender: key-submission@example.net
address: patrice.lumumba@example.net
nonce: f5pscz57zj6fk11wekk8gx4cmrb659a7
#+end_example
and sends it encrypted to the server
#+begin_example
From: patrice.lumumba@example.net
To: key-submission@example.net
Subject: Key publication confirmation
MIME-Version: 1.0
Content-Type: multipart/encrypted;
protocol="application/pgp-encrypted";
boundary="=-=01-iacqg4og4pqz11a5cg1o=-="
Date: Wed, 05 Oct 2016 10:18:52 +0000
--=-=01-iacqg4og4pqz11a5cg1o=-=
Content-Type: application/pgp-encrypted
Version: 1
--=-=01-iacqg4og4pqz11a5cg1o=-=
Content-Type: application/octet-stream
-----BEGIN PGP MESSAGE-----
hF4DUgLY5tvmW2sSAQdAnB1C3PMjS4AsGU0qaCqBdWQO5i6blWEyZrEsY+JZY1Qw
ooNq7zdVWOHhL9LPGAALAgoL3Qfz+dN2u5QamSQ/LJ2c8M0XipNs3lqlNH63yQN1
0sAmAc3W8xkwul+rf6OLK/gMi6WzM4fnUhd4D1LJGIJoNUN0l3636C7ecOt2lkMl
5bVAYg/SyMT3ymyfQnvtiem2T5DSnPsS1g6n6QNXWvkqvX9yGxNsNDJEHTuGJB8k
OJoRlfWQTEo6pgA89febWl1EdeM1pPLstQ2uZE8NPjXoY1nMxAlu+iPYsR41/4sg
dqwOv5BPLh/GIat8hh9SPWCA9iKlgSQ/EIv5DpjQogEzpriT55dkgfvSVYIAcOdO
ShZ91YKkcZffevdY72omqTk10a1SUXehPooIlRFmroDsi3VDaRKrUIo=
=7uve
-----END PGP MESSAGE-----
--=-=01-iacqg4og4pqz11a5cg1o=-=--
#+end_example
* Changes Since -04
- Change to Content-Type "vnd.gnupg.wkd" for servers announcing its
support.
- Require the existance of the Policy Flags file.
- Re-title this I-D to Web Key Directory.
diff --git a/web/index.org b/web/index.org
index db0271e..695c3ab 100644
--- a/web/index.org
+++ b/web/index.org
@@ -1,278 +1,129 @@
#+TITLE: The GNU Privacy Guard
#+STARTUP: showall
#+SETUPFILE: "share/setup.inc"
#+GPGWEB-NEED-SWDB
* The GNU Privacy Guard
#+index: GnuPG
#+index: GPG
#+index: PGP
#+index: Gpg4win
GnuPG is a complete and free implementation of the OpenPGP standard as
defined by [[https://www.ietf.org/rfc/rfc4880.txt][RFC4880]] (also known as /PGP/). GnuPG allows you to encrypt and
sign your data and communications; it features a versatile key management
system, along with access modules for all kinds of public key
directories. GnuPG, also known as /GPG/, is a command line tool with
features for easy integration with other applications. A wealth of
[[file:software/frontends.html][frontend applications]] and [[file:software/libraries.html][libraries]] are available. GnuPG also
provides support for S/MIME and Secure Shell (ssh).
Since its introduction in 1997, GnuPG is [[https://www.gnu.org/philosophy/free-sw.html][Free Software]] (meaning that
it respects your freedom). It can be freely used, modified and
distributed under the terms of the [[https://www.gnu.org/copyleft/gpl.html][GNU General Public License]] .
The current version of GnuPG is {{{gnupg22_ver}}}. See the [[file:download/index.org][download]]
page for other maintained versions.
[[https://www.gpg4win.org][Gpg4win]] is a Windows version of GnuPG featuring a context menu tool, a
crypto manager, and an Outlook plugin to send and receive standard
PGP/MIME mails. The current version of Gpg4win is {{{gpg4win_ver}}}.
* Reconquer your privacy
#+begin_quote
Arguing that you don't care about the right to privacy
because you have nothing to hide is no different from
saying you don't care about free speech because you have
nothing to say. \ndash\nbsp{}Edward\nbsp{}Snowden
#+end_quote
Using encryption helps to protect your privacy and the privacy of the
people you communicate with. Encryption makes life difficult for bulk
surveillance systems. GnuPG is one of the tools that Snowden used to
uncover the secrets of the NSA.
Please visit the [[https://emailselfdefense.fsf.org][Email Self-Defense]] site to learn how and why you
should use GnuPG for your electronic communication. If you need
printed leaflets check out [[https://fsfe.org/contribute/spreadtheword.html#gnupg-leaflet][FSFE’s GnuPG leaflet]].
* News
#+index: News
The latest blog entries:
#+begin_html
#+end_html
The latest release news:\\
([[file:news.org][all news]])
# For those of you who like reading world’s news with an RSS reader,
# GnuPG's latest news are available as [[http://feedvalidator.org/check.cgi?url%3Dhttps://www.gnupg.org/news.en.rss][RSS 2.0 compliant]] feed. Just
# point or paste the [[news.en.rss][RSS file]] into your aggregator.
+** GnuPG 2.2.5 released (2018-02-22)
+
+We are pleased to announce the availability of GnuPG version 2.2.5.
+This is a maintenance release fixing a few problems. {[[https://lists.gnupg.org/pipermail/gnupg-announce/2018q1/000420.html][more]]}
+
** 20 Years of GnuPG (2017-12-20)
Exactly 20 years ago the first public version of GnuPG was released
under the name "g10". Today we are pleased to announce the
availability of GnuPG version 2.2.4. This is a maintenance release
fixing a few minor bugs. {[[https://lists.gnupg.org/pipermail/gnupg-announce/2017q4/000419.html][more]]}
** GnuPG Made Easy 1.10.0 released (2017-12-12)
[[file:software/gpgme/index.org][GPGME]] is a library that allows to add support for cryptography to a
program. {[[https://lists.gnupg.org/pipermail/gnupg-announce/2017q4/000418.html][more]]}
** GnuPG 2.2.3 released (2017-11-21)
We are pleased to announce the availability of GnuPG version 2.2.3.
This is a maintenance release mainly fixing a bug on Windows. The
Windows installer [[https://gpg4win.org][Gpg4win]] 3.0.1 already includes this version of
GnuPG. {[[https://lists.gnupg.org/pipermail/gnupg-announce/2017q4/000417.html][more]]}
** GnuPG 2.2.2 released (2017-11-07)
We are pleased to announce the availability of GnuPG version 2.2.2.
This is a maintenance release fixing a few bugs. {[[https://lists.gnupg.org/pipermail/gnupg-announce/2017q4/000416.html][more]]}
** GnuPG 2.2.1 released (2017-09-19)
We are pleased to announce the availability of GnuPG version 2.2.1.
This is a maintenance release fixing a few minor bugs. {[[https://lists.gnupg.org/pipermail/gnupg-announce/2017q3/000415.html][more]]}
** Libgcrypt 1.8.1 released (2017-08-31) :important:
We are pleased to announce the availability of [[file:software/libgcrypt/index.org][Libgcrypt]] version 1.8.1
and 1.7.9. These releases fix a local side-channel attack on
Curve25519 encryption dubbed "May the Fourth be With You"
[CVE-2017-0379]. Read {[[https://lists.gnupg.org/pipermail/gnupg-announce/2017q3/000414.html][more]]}...
** GnuPG 2.2.0 released (2017-08-28)
The GnuPG team is pleased to announce the availability of a new
GnuPG release: version 2.2.0. Read {[[https://lists.gnupg.org/pipermail/gnupg-announce/2017q3/000413.html][more]]} for details.
This release marks the start of a new long term support series to
replace the 2.0.x series which will reach end-of-life on 2017-12-31.
-** GnuPG 2.1.23 released (2017-08-09)
-
-A new version of GnuPG has been released. Please read the full
-[[https://lists.gnupg.org/pipermail/gnupg-announce/2017q3/000412.html][announcement mail]] for details. This version is intended as a release
-candidate for 2.2.0 which will mark a new long term stable branch.
-
-** GnuPG 2.1.22 released (2017-07-28)
-
-A new version of GnuPG has been released. Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2017q3/000411.html][announcement
-mail]] for details.
-
-Update 2017-07-31: We fixed a problem with keyserver access in the
-Windows versions. A fixed installer has been uploaded; the [[../../download/index.org::binary][download]]
-section has the links.
-
-** GnuPG 1.4.22 released (2017-07-19)
-
-Although GnuPG 1.4 is of limited use today we did a maintenance
-release to address the recently published local side channel attack
-CVE-2017-7526. See the [[../../download/index.org][download]] section on how to get this version.
-
-** Libgcrypt 1.8.0 released (2017-07-18)
-
-We are pleased to announce the availability of [[file:software/libgcrypt/index.org][Libgcrypt]] version
-1.8.0. This is a new stable version with full API and ABI
-compatibility to the 1.7 series. Its main features are support for
-the hash algorithm [[https://en.wikipedia.org/wiki/BLAKE_(hash_function)][Blake-2]], the addition of [[https://en.wikipedia.org/wiki/Disk_encryption_theory][XTS]] mode, an improved
-random number generator, and performance improvements for the [[https://en.wikipedia.org/wiki/ARM_architecture][ARM]]
-architecture. See the [[https://lists.gnupg.org/pipermail/gnupg-announce/2017q3/000410.html][announcement mail]] for details.
-
-** Scute 1.5.0 released (2017-07-14)
-
-Scute is a PKCS#11 module built around the GnuPG Agent and the GnuPG
-Smart Card Daemon. It allows you to use your OpenPGP smart card for TLS
-client authentication and S/MIME mail and document signing.
-Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2017q3/000409.html][announcement mail]] for details.
-
-** Libgcrypt 1.7.8 released (2017-06-29) :important:
-
-We are pleased to announce the availability of [[file:software/libgcrypt/index.org][Libgcrypt]] version
-1.7.8. This release fixes a local side-channel attack
-(CVE-2017-7526). See the [[https://lists.gnupg.org/pipermail/gnupg-announce/2017q2/000408.html][announcement mail]] for details.
-
-** GnuPG 2.1.21 released (2017-05-15) :important:
-
-A new version of GnuPG has been released. This release fixes a
-pubring.gpg corruption bug introduced with 2.1.20. Read the full
-[[https://lists.gnupg.org/pipermail/gnupg-announce/2017q2/000405.html][announcement mail]] for details.
-
-** GnuPG 2.1.20 released (2017-04-03)
-
-A new version of GnuPG has been released. Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2017q2/000404.html][announcement
-mail]] for details.
-
-** New installer for GnuPG 2.1.19 (2017-03-28)
-
-An updated Windows [[https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.1.19_20170328.exe][installer]] for GnuPG 2.1.19 is now available. This
-installer fixes problems retrieving keys for [[https://posteo.de][Posteo]] accounts and other
-servers with limited set of TLS algorithms.
-
-** GnuPG Made Easy 1.9.0 released (2017-03-28)
-
-[[file:software/gpgme/index.org][GPGME]] is a library that allows to add support for cryptography to a
-program. {[[https://lists.gnupg.org/pipermail/gnupg-announce/2017q1/000403.html][more]]}
-
-
-** GnuPG 2.1.19 released (2017-03-01)
-
-A new version of GnuPG has been released. Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2017q1/000402.html][announcement
-mail]] for details.
-
-** GnuPG 2.1.18 released (2017-01-23)
-
-A new version of GnuPG has been released. Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2017q1/000401.html][announcement
-mail]] for details.
-
-** Libgcrypt 1.7.6 released (2017-01-18)
-
-We are pleased to announce the availability of Libgcrypt version
-1.7.6. This is a maintenance release for the stable version of
-[[file:software/libgcrypt/index.org][Libgcrypt]] with a few bug fixes.
-
-** GnuPG 2.1.17 released (2016-12-20)
-
-A new version of GnuPG has been released. Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q4/000400.html][announcement
-mail]] for details.
-
-** Libgcrypt 1.7.5 released (2016-12-15)
-
-We are pleased to announce the availability of Libgcrypt version
-1.7.5. This is a maintenance release for the stable version of
-[[file:software/libgcrypt/index.org][Libgcrypt]] with a few bug fixes. [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q4/000399.html][{more}]]
-
-** Pinentry 1.0.0 released (2016-11-22)
-
-After 14 years is was time to bump up the version of [[file:software/pinentry/index.org][Pinentry]] to 1.0.
-This new release fixes a couple of minor bugs and introduces features
-to better diagnose problems. See the [[../../download/index.org::pinentry][download]] section on how to get
-Pinentry.
-
-** GPA 0.9.10 released (2016-11-19)
-
-A maintenance release of the [[file:software/gpa/index.org][GNU Privacy Assistant]] is now available.
-Note that some of the changes are only available when build with the
-latest [[file:software/gpgme/index.org][GPGME]] version and used with GnuPG 2.1.16 or later.
-
-** GnuPG 2.1.16 released (2016-11-18)
-
-It has been 3 months since the last GnuPG /modern/ release and thus it
-was time for a new one: Version 2.1.16 is now available. Read the
-full [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q4/000398.html][announcement mail]] for details.
-
-** GnuPG Made Easy (GPGME) 1.7.0 released (2016-09-21)
-
-[[file:software/gpgme/index.org][GPGME]] is a library that allows to add support for cryptography to a
-program. Highlights in this release are Python and C++ language
-bindings as well as support for GnuPG 2.1 features. {[[https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000397.html][more]]}
-
-** GnuPG 2.1.15 released (2016-08-18)
-
-A new version of the /modern/ branch of GnuPG has been released.
-Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000396.html][announcement mail]] for details.
-
-** Security fixes for Libgcrypt and GnuPG 1.4 (2016-08-17) :important:
-
-A bug in the random number generator of Libgcrypt and in GnuPG 1.4 has
-been found. Updating the software is highly suggested. Please read
-this [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000395.html][mail]] for details. Note that the CVE id in that mail is not
-correct, the correct one is CVE-2016-6313.
-
-
-* A big Thanks to all supporters
-
-Due to this [[http://www.propublica.org/article/the-worlds-email-encryption-software-relies-on-one-guy-who-is-going-broke][ProPublica article]] we received more than 120,000 \euro of
-individual donations on a single day. There was even more: The [[https://www.linuxfoundation.org/programs/core-infrastructure-initiative][Core
-Infrastructure Initiative]] granted 60,000 $ for 2015. Our payment
-service [[https://twitter.com/stripe/status/563449352635432960][Stripe]] and [[https://www.facebook.com/notes/protect-the-graph/supporting-gnu-privacy-guard/1564591893780956][Facebook]] will each give 50,000 $ to the project.
-And finally the [[https://www.wauland.de/en/donation.html#61][Wau Holland Stiftung]] is collecting tax deductible
-funds for GnuPG (19000 \euro plus 57 BTC).
-
-As the main author of GnuPG, I like to thank everyone for supporting
-the project, be it small or large individual donations, helping users,
-providing corporate sponsorship, working on the software, and for all
-the encouraging words.
-
-GnuPG does not stand alone: there are many other projects, often
-unknown to most people, which are essential to keep the free Internet
-running. Many of them are run by volunteers who spend a lot of unpaid
-time on them. They need our support as well.
-
-/--- Werner, 2015-02-06/
-
-(see also this [[https://gnupg.org/blog/20150310-gnupg-in-february.html][blog]] entry)
-
* COMMENT
This is the publishing info used for the GnuPG pages
#+begin_src emacs-lisp
(progn
(setq gpgweb-root-dir (file-name-directory (buffer-file-name)))
(setq gpgweb-stage-dir (concat gpgweb-root-dir "../stage"))
(require 'gpgweb (concat gpgweb-root-dir "share/gpgweb.el"))
(setq org-publish-use-timestamps-flag nil)
(setq org-export-html-toplevel-hlevel 1)
(setq org-export-html-coding-system 'utf-8)
(gpgweb-setup-project))
#+end_src
diff --git a/web/news.org b/web/news.org
index 5f85932..b78040c 100644
--- a/web/news.org
+++ b/web/news.org
@@ -1,1659 +1,1790 @@
#+TITLE: GnuPG - All News
#+STARTUP: showall
* All News
On this page you'll find all the news of previous years in reverse
chronological order. News for the current year are found at the [[index][main
page]].
+
+** GnuPG 2.1.23 released (2017-08-09)
+
+A new version of GnuPG has been released. Please read the full
+[[https://lists.gnupg.org/pipermail/gnupg-announce/2017q3/000412.html][announcement mail]] for details. This version is intended as a release
+candidate for 2.2.0 which will mark a new long term stable branch.
+
+** GnuPG 2.1.22 released (2017-07-28)
+
+A new version of GnuPG has been released. Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2017q3/000411.html][announcement
+mail]] for details.
+
+Update 2017-07-31: We fixed a problem with keyserver access in the
+Windows versions. A fixed installer has been uploaded; the [[../../download/index.org::binary][download]]
+section has the links.
+
+** GnuPG 1.4.22 released (2017-07-19)
+
+Although GnuPG 1.4 is of limited use today we did a maintenance
+release to address the recently published local side channel attack
+CVE-2017-7526. See the [[../../download/index.org][download]] section on how to get this version.
+
+** Libgcrypt 1.8.0 released (2017-07-18)
+
+We are pleased to announce the availability of [[file:software/libgcrypt/index.org][Libgcrypt]] version
+1.8.0. This is a new stable version with full API and ABI
+compatibility to the 1.7 series. Its main features are support for
+the hash algorithm [[https://en.wikipedia.org/wiki/BLAKE_(hash_function)][Blake-2]], the addition of [[https://en.wikipedia.org/wiki/Disk_encryption_theory][XTS]] mode, an improved
+random number generator, and performance improvements for the [[https://en.wikipedia.org/wiki/ARM_architecture][ARM]]
+architecture. See the [[https://lists.gnupg.org/pipermail/gnupg-announce/2017q3/000410.html][announcement mail]] for details.
+
+** Scute 1.5.0 released (2017-07-14)
+
+Scute is a PKCS#11 module built around the GnuPG Agent and the GnuPG
+Smart Card Daemon. It allows you to use your OpenPGP smart card for TLS
+client authentication and S/MIME mail and document signing.
+Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2017q3/000409.html][announcement mail]] for details.
+
+** Libgcrypt 1.7.8 released (2017-06-29) :important:
+
+We are pleased to announce the availability of [[file:software/libgcrypt/index.org][Libgcrypt]] version
+1.7.8. This release fixes a local side-channel attack
+(CVE-2017-7526). See the [[https://lists.gnupg.org/pipermail/gnupg-announce/2017q2/000408.html][announcement mail]] for details.
+
+** GnuPG 2.1.21 released (2017-05-15) :important:
+
+A new version of GnuPG has been released. This release fixes a
+pubring.gpg corruption bug introduced with 2.1.20. Read the full
+[[https://lists.gnupg.org/pipermail/gnupg-announce/2017q2/000405.html][announcement mail]] for details.
+
+** GnuPG 2.1.20 released (2017-04-03)
+
+A new version of GnuPG has been released. Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2017q2/000404.html][announcement
+mail]] for details.
+
+** New installer for GnuPG 2.1.19 (2017-03-28)
+
+An updated Windows [[https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.1.19_20170328.exe][installer]] for GnuPG 2.1.19 is now available. This
+installer fixes problems retrieving keys for [[https://posteo.de][Posteo]] accounts and other
+servers with limited set of TLS algorithms.
+
+** GnuPG Made Easy 1.9.0 released (2017-03-28)
+
+[[file:software/gpgme/index.org][GPGME]] is a library that allows to add support for cryptography to a
+program. {[[https://lists.gnupg.org/pipermail/gnupg-announce/2017q1/000403.html][more]]}
+
+
+** GnuPG 2.1.19 released (2017-03-01)
+
+A new version of GnuPG has been released. Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2017q1/000402.html][announcement
+mail]] for details.
+
+** GnuPG 2.1.18 released (2017-01-23)
+
+A new version of GnuPG has been released. Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2017q1/000401.html][announcement
+mail]] for details.
+
+** Libgcrypt 1.7.6 released (2017-01-18)
+
+We are pleased to announce the availability of Libgcrypt version
+1.7.6. This is a maintenance release for the stable version of
+[[file:software/libgcrypt/index.org][Libgcrypt]] with a few bug fixes.
+
+** GnuPG 2.1.17 released (2016-12-20)
+
+A new version of GnuPG has been released. Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q4/000400.html][announcement
+mail]] for details.
+
+** Libgcrypt 1.7.5 released (2016-12-15)
+
+We are pleased to announce the availability of Libgcrypt version
+1.7.5. This is a maintenance release for the stable version of
+[[file:software/libgcrypt/index.org][Libgcrypt]] with a few bug fixes. [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q4/000399.html][{more}]]
+
+** Pinentry 1.0.0 released (2016-11-22)
+
+After 14 years is was time to bump up the version of [[file:software/pinentry/index.org][Pinentry]] to 1.0.
+This new release fixes a couple of minor bugs and introduces features
+to better diagnose problems. See the [[../../download/index.org::pinentry][download]] section on how to get
+Pinentry.
+
+** GPA 0.9.10 released (2016-11-19)
+
+A maintenance release of the [[file:software/gpa/index.org][GNU Privacy Assistant]] is now available.
+Note that some of the changes are only available when build with the
+latest [[file:software/gpgme/index.org][GPGME]] version and used with GnuPG 2.1.16 or later.
+
+** GnuPG 2.1.16 released (2016-11-18)
+
+It has been 3 months since the last GnuPG /modern/ release and thus it
+was time for a new one: Version 2.1.16 is now available. Read the
+full [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q4/000398.html][announcement mail]] for details.
+
+** GnuPG Made Easy (GPGME) 1.7.0 released (2016-09-21)
+
+[[file:software/gpgme/index.org][GPGME]] is a library that allows to add support for cryptography to a
+program. Highlights in this release are Python and C++ language
+bindings as well as support for GnuPG 2.1 features. {[[https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000397.html][more]]}
+
+** GnuPG 2.1.15 released (2016-08-18)
+
+A new version of the /modern/ branch of GnuPG has been released.
+Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000396.html][announcement mail]] for details.
+
+** Security fixes for Libgcrypt and GnuPG 1.4 (2016-08-17) :important:
+
+A bug in the random number generator of Libgcrypt and in GnuPG 1.4 has
+been found. Updating the software is highly suggested. Please read
+this [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000395.html][mail]] for details. Note that the CVE id in that mail is not
+correct, the correct one is CVE-2016-6313.
+
** GnuPG 2.1.14 released (2016-07-14)
A new version of the /modern/ branch of GnuPG has been released.
Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000393.html][announcement mail]] for details.
** Libgcrypt 1.7.2 released (2016-07-14)
We are pleased to announce the availability of Libgcrypt version
1.7.2. This is a maintenance release for the stable version of
[[file:software/libgcrypt/index.org][Libgcrypt]] with a few bug fixes. [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000392.html][{more}]]
** GnuPG 2.1.13 released (2016-06-16)
A new version of the /modern/ branch of GnuPG has been released.
Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q2/000390.html][announcement mail]] for details.
** Libgcrypt 1.7.1 released (2016-06-15)
We are pleased to announce the availability of Libgcrypt version
1.7.1. This is a maintenance release for the stable version of
[[file:software/libgcrypt/index.org][Libgcrypt]] with a few bug fixes. [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q2/000389.html][{more}]]
** First OpenPGP conference (2016-05-20)
If you are a user or implementer of OpenPGP related software, you may
join us at [[https://gnupg.org/conf/][OpenPGP.conf]] in Cologne on September 8 and 9, 2016.
** GnuPG 2.1.12 released (2016-05-04)
A new version of the /modern/ branch of GnuPG has been released.
Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q2/000387.html][announcement mail]] for details.
** Libgcrypt 1.7.0 released (2016-04-15)
We are pleased to announce the availability of Libgcrypt version
1.7.0. This is a new stable version of [[file:software/libgcrypt/index.org][Libgcrypt]] with full API and
ABI compatibiliy to the 1.6 series. Its main features are new
algorithms, curves, and performance improvements. [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q2/000386.html][{more}]]
** GnuPG 2.0.30 released (2016-03-31)
GnuPG 2.0.30 is now available. This release fixes a few minor bugs;
users of GnuPG 2.0.x may want to update to this version. [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q1/000385.html][{more}]]
** Libgcrypt 1.6.5 released (2016-02-09) :important:
Libgcrypt version 1.6.5 and an updated Windows installer for GnuPG
2.1.11 has been released to mitigate a new side-channel attack.
[[https://lists.gnupg.org/pipermail/gnupg-announce/2016q1/000384.html][{more}]]
** GnuPG 2.1.11 released (2016-01-26)
A new version of the /modern/ branch of GnuPG has been released.
Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2016q1/000383.html][announcement mail]] for details.
** GnuPG 1.4.20 released (2015-12-20)
18 years after the first GnuPG release version 1.4.20 has been
released today. This release from the /classic/ branch of GnuPG now
also rejects the insecure MD5 signatures created by PGP-2 (unless the
=--pgp2= option is used). [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q4/000382.html][{more}]]
** GnuPG 2.1.10 released (2015-12-04)
A new version of the /modern/ branch of GnuPG has been released. The
main features of this release are support for [[https://en.wikipedia.org/wiki/Trust_on_first_use][TOFU]] and anonymous key
retrieval via [[https://www.torproject.org][Tor]]. Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q4/000381.html][announcement mail]] for details.
** GnuPG 2.1.9 released (2015-10-09)
A new version of the /modern/ branch of GnuPG has been released.
Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q4/000380.html][announcement mail]] for details.
** GnuPG 2.1.8 released (2015-09-10)
A new version of the /modern/ branch of GnuPG has been released.
Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q3/000379.html][announcement mail]] for details.
** GPA 0.9.9 released (2015-09-09)
A new version of [[file:software/gpa/index.org][GPA]], the graphical frontend for GnuPG, is now
available. This release fixes a couple of bugs and has been changed
to show the clipboard view on startup. [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q3/000378.html][{more}]]
** GnuPG 2.0.29 released (2015-09-08)
GnuPG 2.0.29 is now available. This release fixes a couple of bugs;
users of GnuPG 2.0.x may want to update to this version. [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q3/000376.html][{more}]]
** Libgcrypt 1.6.4 released (2015-09-08)
Libgcrypt version 1.6.4 has been released to fix a few minor bugs and
a crash on newer Windows versions. [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q3/000375.html][{more}]]
** Libassuan 2.3.0 released (2015-08-28)
[[file:software/libassuan/index.org][Libassuan]] is a generic [[https://en.wikipedia.org/wiki/Inter-process_communication][IPC]] library used by GnuPG, GPGME, and a few
other packages. This release fixes two bugs and introduces new
support functions for the socket wrappers. See [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q3/000374.html][here]] for details.
** GPGME 1.6.0 and Libgpg-error 1.20 released (2015-08-26)
GPGME 1.6.0 is now available. This release introduce a mode to export
sceret keys, improves the error return codes, and is prepared to make
use of the GnuPG 2.1 Windows installer. See this full [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q3/000372.html][announcement]].
An update of Libgpg-error to fix a problem in Windows has also been
released; see this [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q3/000373.html][announcement]].
** GnuPG 2.1.7 released (2015-08-11)
A new version of the /modern/ branch of GnuPG has been released.
Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q3/000371.html][announcement mail]] for details.
** GnuPG 2.1.6 released (2015-07-01)
A new version of the /modern/ branch of GnuPG has been released.
Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q3/000370.html][announcement mail]] for details.
** GnuPG 2.1.5 released (2015-06-11)
A new version of the /modern/ branch of GnuPG has been released.
Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q2/000369.html][announcement mail]] for details.
** GPGME 1.5.5 released (2015-06-08)
GPGME 1.5.5 is now available. This release fixes a crash due to
malformed user ids and a regression when gpgsm < 2.1 is used. See the
full [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q2/000368.html][{announcement}]] mail.
** GnuPG 2.0.28 released (2015-06-02)
GnuPG 2.0.28 is now available. This release fixes a couple of bugs;
users of GnuPG 2.0.x should update to this version. [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q2/000367.html][{more}]]
** GnuPG 2.1.4 released (2015-05-12)
A new version of the /modern/ branch of GnuPG has been released.
Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q2/000366.html][announcement mail]] for details.
** GnuPG 2.1.3 released (2015-04-11)
This is another release of the /modern/ branch of GnuPG. It fixes
a lot of bugs. Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q2/000365.html][announcement mail]].
** GnuPG 1.4.19 released (2015-02-27) :important:
GnuPG 1.4.19 is now available. This release mitigates two new of side
channel attack methods as well as a couple of other bugs. [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q1/000363.html][{more}]]
** Libgcrypt 1.6.3 released (2015-02-27) :important:
Libgcrypt version 1.6.3 has been released to mitigate two new side
channel attack methods. [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q1/000364.html][{more}]]
** GnuPG 2.0.27 released (2015-02-18)
GnuPG 2.0.27 is now available. This release fixes a couple of bugs;
users of GnuPG 2.0.x should update to this version. [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q1/000362.html][{more}]]
** GnuPG 2.1.2 released (2015-02-11)
This is the third release of the /modern/ branch of GnuPG. It fixes
a lot of bugs. Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2015q1/000361.html][announcement mail]].
** GnuPG 2.1.1 released (2014-12-16)
This is the second release of the /modern/ branch of GnuPG. It fixes
a lot of bugs and brings some new features. Read more about 2.1 at
the [[file:faq/whats-new-in-2.1.org][feature overview]] page and in the [[https://lists.gnupg.org/pipermail/gnupg-announce/2014q4/000360.html][announcement]] mail.
** Libksba 1.3.2 released (2014-11-25) :important:
This is a security fix release and all users of Libksba should update
to this version. Note that *GnuPG 2.x* makes use of Libksba and thus
all user of GnuPG 2.x need to install this new version of Libksba and
restart the dirmngr process. Read the full [[https://lists.gnupg.org/pipermail/gnupg-announce/2014q4/000359.html][announcement]].
** GnuPG 2.1.0 with ECC support released (2014-11-06)
This is the first release of the new /modern/ branch of GnuPG. It
features a lot of new things including support for ECC. Read more at
the [[file:faq/whats-new-in-2.1.org][feature overview]] page and in the [[https://lists.gnupg.org/pipermail/gnupg-announce/2014q4/000358.html][announcement]] mail.
** A beta for GnuPG 2.1.0 released (2014-10-03)
A beta release for the forthcoming GnuPG 2.1 version is now
available. [[https://lists.gnupg.org/pipermail/gnupg-announce/2014q4/000357.html][{more}]]
** GPA 0.95 released
GPA is the GNU Privacy Assistant, a frontend to GnuPG. This new
release has support for ECC keys and improves on the UI server
feature. [[https://lists.gnupg.org/pipermail/gnupg-announce/2014q3/000356.html][{more}]]
** GnuPG 2.0.26 released (2014-08-12)
GnuPG 2.0.26 is now available. This is a maintenance release. [[https://lists.gnupg.org/pipermail/gnupg-announce/2014q3/000353.html][{more}]]
** Libgcrypt 1.5.4 security fix release :important:
Using any Libgcrypt version less than 1.5.4 with GnuPG 2.0.x and
Elgamal encryption keys is vulnerable to the /Get Your Hands Off My
Laptop/ attack. Please update to the newly released Libgcrypt 1.5.4
or a 1.6 version. [[https://lists.gnupg.org/pipermail/gnupg-announce/2014q3/000352.html][{more}]]
** Get Your Hands Off My Laptop (2014-08-07)
Daniel Genkin, Itamar Pipman, and Eran Tromer latest side channel
attack targets an /older version/ of GnuPG. If your GnuPG and
Libgcrypt versions are up-to-date you are safe. [[https://lists.gnupg.org/pipermail/gnupg-announce/2014q3/000349.html][{more}]]
** GPGME 1.5.1 and 1.4.4 released (2014-08-07) :important:
A security fix release for the GPGME library is available. It is
suggested to update to one of these version. [[https://lists.gnupg.org/pipermail/gnupg-announce/2014q3/000350.html][{more}]]
** GnuPG 2.0.25 and 1.4.18 released (2014-06-30)
To fix a minor regression in the previous releases we released today
new versions of GnuPG-1 and GnuPG-2: [[https://lists.gnupg.org/pipermail/gnupg-announce/2014q2/000346.html][{2.0.25}]], [[https://lists.gnupg.org/pipermail/gnupg-announce/2014q2/000347.html][{1.4.18}]]
** GnuPG 2.0.24 released (2014-06-24) :important:
GnuPG 2.0.24 is now available. This GnuPG-2 release features a fix
for a denial of service attack and a few other changes. [[https://lists.gnupg.org/pipermail/gnupg-announce/2014q2/000345.html][{more}]]
** GnuPG 1.4.17 released (2014-06-23) :important:
GnuPG 1.4.17 is now available. This GnuPG-1 release features a fix
for a denial of service attack and a few other minor changes. [[https://lists.gnupg.org/pipermail/gnupg-announce/2014q2/000344.html][{more}]]
** GnuPG 2.0.23 released (2014-06-03)
We are pleased to announce the availability of GnuPG 2.0.23. This is
a maintenance release with a few new features. [[https://lists.gnupg.org/pipermail/gnupg-announce/2014q2/000342.html][{more}]]
** Goteo campaign: preliminary results (2014-05-12)
The blog has a report on the current status of the campaign including
an overview of the financial results. [[https://www.gnupg.org/blog/20140512-rewards-sent.html][{read here}]]
** Mission complete: campaign ends, closing stats (2014-02-06)
After 50 days of crowdfunding, the GnuPG campaign for new website and
infrastructure will close tomorrow. That means rewards for backers can
now be ordered and preparations for dispatch can begin. Here are the
results so far. [[https://www.gnupg.org/blog/20140206-crowdfunding-complete.html][{more}]]
** 16 Years of protecting privacy (2013-12-20)
Today marks 16 years since the first release of GnuPG. In that time
the project has grown from being a hacker’s hobby into one of the
world’s most critical anti-surveillance tools. Today GnuPG stands at
the front line of the battle between invasive surveillance and civil
liberties. [[https://www.gnupg.org/blog/20131220-gnupg-turned-0x10.html][{more}]]
** GnuPG launches crowdfunding campaign (2013-12-19)
Today GNU Privacy Guard (GnuPG) has launched its first
[[http://goteo.org/project/gnupg-new-website-and-infrastructure][crowdfunding campaign]] with the aim of building a new website and long term
infrastructure. [[https://lists.gnupg.org/pipermail/gnupg-announce/2013q4/000338.html][{more}]] [[https://www.gnupg.org/blog/20131219-gnupg-launches-crowfunding.de.html][{deutsch}]] [[https://www.gnupg.org/blog/20131219-gnupg-launches-crowfunding.fr.html][{francaise}]]
** GnuPG 1.4.16 released (2013-12-18) :important:
Along with the publication of an interesting new [[http://www.cs.tau.ac.il/~tromer/acoustic/][side channel attack]]
by Genkin, Shamir, and Tromer we announce the availability of a new
stable GnuPG release to relieve this bug: Version 1.4.16 ... [[https://lists.gnupg.org/pipermail/gnupg-announce/2013q4/000337.html][{more}]]
** Blog: Getting Goteo crowdfunding approval (2013-12-18)
The targets are set, the rewards are prepared, the press release has
been edited and translated, and now we're waiting for approval from
the crowdfunding platform Goteo ... [[https://www.gnupg.org/blog/20131218-getting-goteo-approval.html][{more}]]
** GnuPG 1.4.16 released (2013-12-18) :important:
Along with the publication of an interesting new [[http://www.cs.tau.ac.il/~tromer/acoustic/][side channel attack]]
by Genkin, Shamir, and Tromer we announce the availability of a new
stable GnuPG release to relieve this bug: Version 1.4.16 ... [[https://lists.gnupg.org/pipermail/gnupg-announce/2013q4/000337.html][{more}]]
** Libgcrypt 1.6.0 released (2013-10-16)
The GNU project is pleased to announce the availability of Libgcrypt
version 1.6.0. This is the new stable version of Libgcrypt with the API
being mostly compatible to previous versions. Due to the removal of
certain long deprecated functions this version introduces an ABI
change.
The main features of this version are performance improvements,
better support for elliptic curves, new algorithms and modes, as well as
API and internal cleanups. [[https://lists.gnupg.org/pipermail/gnupg-announce/2013q4/000336.html][{more}]]
** Blog: Preparing for launch (2013-12-13)
Mid December, giving season, and nearly time for the GnuPG Crowdfunding
to commence. We've been working hard on preparations ...
[[https://www.gnupg.org/blog/index.html][{more}]]
** Blog: Friends tell friends they love GnuPG (2013-11-13)
Using GnuPG for email encryption takes two to tango. That's why
we're asking users to share their stories using #iloveGPG ...
[[https://www.gnupg.org/blog/index.html][{more}]]
** New website infrastructure (2013-11-12)
After more than a decade we switched from the legacy WML based website
system to a new [[http://org-mode.org][org-mode]] based one. The old WML code was not anymore
maintainable and building the website took way to long. The new
system uses plain text files and will make it way easier to keep
information up to date. Unfortunately the translations are gone for
now --- most of them have not been updated for many years anyway.
** Blog: Securing the future of GPG (2013-11-05)
We have a plan for securing the long term stability of GnuPG
development by giving more to our users, and asking more from them in
return ... [[https://www.gnupg.org/blog/index.html][{more}]]
** Security update for GnuPG (2013-10-05) :important:
We are pleased to announce the availability of a new stable GnuPG
release: Version 2.0.22 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2013q4/000333.html][{more}]]
** Security update for GnuPG (2013-10-05) :important:
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.4.15 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2013q4/000334.html][{more}]]
** GnuPG 2.0.21 released (2013-08-19)
We are pleased to announce the availability of GnuPG 2.0.21. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2013q3/000332.html][{more}]]
** Security update for GnuPG (2013-07-25) :important:
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.4.14 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2013q3/000329.html][{more}]]
** Security update for Libgcrypt (2013-07-25) :important:
We are pleased to announce the availability of a new stable Libgcrypt
release: Version 1.5.3 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2013q3/000329.html][{more}]]
** GnuPG 2.0.20 released (2013-05-10 18:59:01)
We are pleased to announce the availability of GnuPG 2.0.20. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2013q2/000328.html][{more}]]
** GnuPG 1.4.13 released (2012-12-20 21:51:56)
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.4.13 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2012q4/000319.html][{more}]]
** GnuPG 2.0.19 released (2012-03-27 11:22:13)
We are pleased to announce the availability of GnuPG 2.0.19. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2012q1/000314.html][{more}]]
** GnuPG 1.4.12 released (2012-01-30 17:39:22)
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.4.12 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2012q1/000313.html][{more}]]
** GnuPG 1.4.13 released (2012-12-20 21:51:56)
Wir freuen uns, Ihnen die Verfügbarkeit von GnuPG 1.4.13 bekannt
zu geben.
[[https://lists.gnupg.org/pipermail/gnupg-announce/2012q4/000319.html][{more}]]
** GnuPG 2.0.19 released (2012-03-27 11:22:13)
We are pleased to announce the availability of GnuPG 2.0.19. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2012q1/000314.html][{more}]]
** GnuPG 1.4.12 released (2012-01-30 17:39:22)
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.4.12. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2012q1/000313.html][{more}]]
** STEED project announced (2011-10-17 20:15:22)
STEED - Usable end-to-end encryption ...
[[https://lists.gnupg.org/pipermail/gnupg-devel/2011-October/026264.html][{more}]]
** GnuPG 2.0.18 released (2011-08-04 18:19:36)
We are pleased to announce the availability of GnuPG 2.0.18. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2011q3/000312.html][{more}]]
** Libgcrypt 1.5.0 released (2011-06-29 12:21:39)
We are pleased to announce the availability of Libgcrypt 1.5.0. This is
the new stable version of Libgcrypt and upward compatible with the 1.4
series. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2011q2/000307.html][{more}]]
** GnuPG 2.0.17 released (2011-01-13 17:20:12)
We are pleased to announce the availability of GnuPG 2.0.17. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2011q1/000305.html][{more}]]
** GnuPG 1.4.11 released (2010-10-18 13:36:14)
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.4.11 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2010q4/000303.html][{more}]]
** Important security update for GnuPG (2010-07-23 14:38:50)
While trying to import a server certificate for a CDN service, a segv
bug was found in GnuPG's GPGSM tool. It is likely that this bug is
exploitable by sending a special crafted signed message and having a
user verify the signature. A simple patch is available ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2010q3/000302.html][{more}]]
** GnuPG 2.0.16 released (2010-07-19 10:44:59)
We are pleased to announce the availability of GnuPG 2.0.16. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2010q3/000301.html][{more}]]
** GnuPG 2.0.15 released (2010-03-09 11:44:13)
We are pleased to announce the availability of GnuPG 2.0.15. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2010q1/000299.html][{more}]]
** GnuPG 2.0.14 released (2009-12-21 19:03:26)
We are pleased to announce the availability of GnuPG 2.0.14. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2009q4/000296.html][{more}]]
** Libgcrypt 1.4.5 released (2009-12-11 17:51:12)
We are pleased to announce the availability of Libgcrypt 1.4.5. This is
the new stable version of Libgcrypt and upward compatible with the 1.2
series. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2009q4/000295.html][{more}]]
** GnuPG 2.0.13 released (2009-09-04 19:12:01)
We are pleased to announce the availability of GnuPG 2.0.13. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2009q3/000294.html][{more}]]
** GnuPG 1.4.10 released (2009-09-02 19:27:55)
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.4.10 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2009q3/000291.html][{more}]]
** GnuPG 2.0.12 released (2009-06-17 13:19:26)
We are pleased to announce the availability of GnuPG 2.0.12. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2009q2/000288.html][{more}]]
** GnuPG 2.0.11 released (2009-03-03 13:02:51)
We are pleased to announce the availability of GnuPG 2.0.11 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2009q1/000287.html][{more}]]
** Libgcrypt 1.4.4 released (2009-01-22 20:08:24)
We are pleased to announce the availability of Libgcrypt 1.4.4. This is
the new stable version of Libgcrypt and upward compatible with the 1.2
series. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2009q1/000285.html][{more}]]
** GnuPG 2.0.10 released (2009-01-12 10:59:05)
We are pleased to announce the availability of GnuPG 2.0.10 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2009q1/000284.html][{more}]]
** Signing key updated! (2009-01-09 12:58:02)
The expiration date of the key used to sign GnuPG distributions has been
prolonged for another year. Please update the key ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2009q1/000282.html][{more}]]
** GnuPG's 10th birthday! (2007-12-20 12:10:30)
It has been a decade since the very first version of the GNU Privacy
Guard was released ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2007q4/000268.html][{more}]]
** GnuPG 2.0.8 released (2007-12-20 12:09:30)
We are pleased to announce the availability of GnuPG 2.0.8 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2007q4/000267.html][{more}]]
** GnuPG 1.4.8 released (2007-12-20 12:09:03)
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.4.8. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2007q4/000266.html][{more}]]
** Libgcrypt 1.4.0 released (2007-12-10 20:10:34)
We are pleased to announce the availability of Libgcrypt 1.4.0. This is
the new stable version of Libgcrypt and upward compatible with the 1.2
series. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2007q4/000263.html][{more}]]
** New OpenPGP standard (2007-11-02 17:54:26)
The new OpenPGP standard has been published. It was assigned RFC number
4880. ...
[[https://lists.gnupg.org/pipermail/gnupg-users/2007-November/031994.html][{more}]]
** GnuPG 2.0.7 released (2007-09-10 19:18)
We are pleased to announce the availability of GnuPG 2.0.7 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2007q3/000259.html][{more}]]
** GnuPG 2.0.6 released (2007-08-16 17:48)
We are pleased to announce the availability of GnuPG 2.0.6 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2007q3/000258.html][{more}]]
** GnuPG 2.0.5 released (2007-07-06 12:46)
We are pleased to announce the availability of GnuPG 2.0.5 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2007q3/000255.html][{more}]]
** Manual pages online (2007-05-11 11:45:30)
The manuals of GnuPG and some related software are now available online.
Check out the navigation bar or go directly to the
[[https://www.gnupg.org/documentation/manuals.html][overview page]] .
** GnuPG 2.0.4 released (2007-05-09 13:02)
We are pleased to announce the availability of GnuPG 2.0.4 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2007q2/000254.html][{more}]]
** GnuPG 2.0.3 released (2007-03-08 16:55:25)
We are pleased to announce the availability of GnuPG 2.0.3 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2007q1/000252.html][{more}]]
** Multiple Messages Problem in GnuPG and GPGME (2007-03-06 09:31:21)
A common usage problem of gpg has been identified. Instead of requiring
a fix for all these applications, GnuPG and GPGME have been changed to
provide the necessary protection. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2007q1/000251.html][{more}]]
** Important security update for GnuPG(2006-12-06 17:18:35)
Tavis Ormandy of the Gentoo security team identified a severe and
exploitable bug in the processing of encrypted packets in GnuPG.
Updating is highly suggested. A new version of GnuPG (1.4.6) as well has
a patch to 2.0.1 has been released. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2006q4/000246.html][{more}]]
** Announcing the winner of the logo contest (2006-12-02 19:37:04)
And the winner is: Thomas Wittek ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2006q4/000244.html][{more}]]
** GnuPG 2.0.1 released (2006-11-29 15:14:13)
We are pleased to announce the availability of GnuPG 2.0.1 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2006q4/000242.html][{more}]]
** Dirmngr 1.0.0 released (2006-11-29 15:14:13)
We are pleased to announce the availability of Dirmngr 1.0.0 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2006q4/000243.html][{more}]]
** GnuPG 2.0 released (2006-11-13 12:43:16)
We are pleased to announce the availability of GnuPG 2.0.0 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2006q4/000239.html][{more}]]
** GnuPG 1.9.92 released (2006-10-11 13:43:29)
We are pleased to announce the availability of GnuPG 1.9.92 - one of the
last steps towards a 2.0 release. ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2006q4/000236.html][{more}]]
** GnuPG Logo contest (2006-09-19 14:43:08)
After 8 years the time has come to modernize the GnuPG Logo and to work
on a new layout of the website ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2006q3/000235.html][{more}]]
** Gpg4win 1.0.6 released (2006-08-29 09:52:50)
We are pleased to announce the availibility of Gpg4win, version 1.0.6
...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2006q3/000232.html][{more}]]
** Libgcrypt 1.2.3 released (2006-08-29 09:49:39)
We are pleased to announce the availability of Libgcrypt 1.2.3. Since
this is a bugfix release, it does not include any new features...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2006q3/000231.html][{more}]]
** GnuPG 1.4.5 released (2006-08-01 17:42:11)
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.4.5 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2006q3/000229.html][{more}]]
** GnuPG 1.4.4 released (2006-06-25 15:57:40)
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.4.4 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2006q2/000226.html][{more}]]
** Gpg4win 1.0.1 released (2006-04-26 13:29:58)
We are pleased to announce the availibility of Gpg4win, version 1.0.1
...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2006q2/000224.html][{more}]]
** Gpg4win released (2006-04-03 14:28:36)
After struggling for 6 month with Windows pecularities, we are finally
pleased to announce the first stable release of Gpg4win, version
1.0.0...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2006q2/000223.html][{more}]]
** GnuPG 1.4.3 released (2006-04-03 14:28:36)
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.4.3 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2006q2/000222.html][{more}]]
** GnuPG does not detect injection of unsigned data (2006-03-09 20:02:28)
In the aftermath of the false positive signature verification bug more
thorough testing of the fix has been done and another vulnerability has
been detected. This new problem affects the use of gpg for verification
of signatures which are not detached signatures. The problem also
affects verification of signatures embedded in encrypted messages; i.e.
standard use of gpg for mails. Update GnuPG as soon as possible to
version 1.4.2.2!
[[https://lists.gnupg.org/pipermail/gnupg-announce/2006q1/000216.html][{more}]]
** False positive signature verification in GnuPG (2006-02-15 12:43:54)
The Gentoo project identified a security related bug in GnuPG. When
using any current version of GnuPG for unattended signature verification
(e.g. by scripts and mail programs), false positive signature
verification of detached signatures may occur. This problem affects the
tool *gpgv*, as well as using "gpg --verify" to imitate gpgv, if only
the exit code of the process is used to decide whether a detached
signature is valid.
[[https://lists.gnupg.org/pipermail/gnupg-announce/2006q1/000211.html][{more}]]
** GnuPG 1.9.20 (S/MIME and gpg-agent) released (2005-12-20 12:56:31)
We are pleased to announce the availability of GnuPG 1.9.20 - the branch
of GnuPG featuring the S/MIME...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2005q4/000209.html][{more}]]
** Libgcrypt 1.2.2 released (2005-10-05 15:34:42)
We are pleased to announce the availability of Libgcrypt 1.2.2. Since
this is a bugfix release, it does not include any new features...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2005q4/000205.html][{more}]]
** GnuPG 1.9.19 (S/MIME and gpg-agent) released (2005-09-12 15:29:20)
We are pleased to announce the availability of GnuPG 1.9.19 - the branch
of GnuPG featuring the S/MIME...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2005q3/000204.html][{more}]]
** GnuPG Explorer Extension (GPGee) version 1.2.1 released (2005-09-08 14:41:58)
Version 1.2.1 of GPGee has now been released and is available at...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2005q3/000203.html][{more}]]
** GnuPG Explorer Extension (GPGee) version 1.2.0 released (2005-09-06 16:09:57)
Version 1.2.0 of GPGee has been released - head to the homepage at...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2005q3/000202.html][{more}]]
** GPGee version 1.1.2 - Important Security Update (2005-07-30 00:29:18)
Version 1.1.2 of GPGee has been released. This release fixes a newly
identified security issue...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2005q3/000201.html][{more}]]
** GnuPG 1.4.2 released (2005-07-27 09:53:27)
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.4.2 ...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2005q3/000200.html][{more}]]
** GPGee (GnuPG Explorer Extension) version 1.1.1 (2005-07-18 04:58:16)
I have released version 1.1.1 of GPGee. This is a minor update to 1.1 to
answer a couple user...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2005q3/000199.html][{more}]]
** Second release candidate for GnuPG 1.4.2 available (2005-06-21 16:44:35
CET)
We are pleased to announce the availability of another release candidate
for the forthcoming 1.4.2 version of gnupg...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2005q2/000198.html][{more}]]
** GnuPG 1.9.17 (S/MIME and gpg-agent) released (2005-06-20 21:58:24 CET)
We are pleased to announce the availability of GnuPG 1.9.17; the
development branch of GnuPG featuring the S/MIME protocol...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2005q2/000196.html][{more}]]
** First release candidate for GnuPG 1.4.2 available (2005-05-31 14:27:33 CET)
We are pleased to announce the availability of a release candidate for
the forthcoming 1.4.2 version of gnupg...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2005q2/000195.html][{more}]]
** GnuPG 1.9.16 (S/MIME) released (2005-04-21 17:23:56 CET)
We are pleased to announce the availability of GnuPG 1.9.16; the
development branch of GnuPG featuring the S/MIME protocol...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2005q2/000194.html][{more}]]
** GnuPG 1.4.1 News (2005-03-15 17:53:36 CET)
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.4.1...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2005q2/000192.html][{more}]]
** Smartcard daemon and gpg's S/MIME cousin gpgsm (2005-02-23 12:43:27 CET)
The design is different to the previous versions and we may not support
all ancient...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2005q2/000177.html][{more}]]
** Attack against OpenPGP encryption (2005-02-11 02:00:17 CET)
Last night, Serge Mister and Robert Zuccherato published a paper
reporting on an attack against OpenPGP symmetric encryption...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2005q1/000191.html][{more}]]
** Libgcrypt 1.2.1 released (2005-01-09 15:03:22 CET)
We are pleased to announce the availability of Libgcrypt 1.2.1. Since
this is a bugfix release, it does not include any new features...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2005q1/000189.html][{more}]]
** GnuPG 1.2.7 released (2004-12-28 11:54:32 CET)
As promised in the announcement of GnuPG 1.4.0, we are now pleased to
announce the availability GnuPG 1.2.7...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2004q4/000188.html][{more}]]
** Updated GnuPG 1.4.0 Windows binary (2004-12-16 22:17:10 CET)
A couple of hours ago we announced GnuPG 1.4.0, claiming that a compiled
version for MS Windows is also available. Unfortunately that Windows
version...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2004q4/000187.html][{more}]]
** GnuPG stable 1.4 released (2004-12-16 18:24:48 CET)
We are pleased to announce the availability of the new stable GnuPG
series. This first release is version 1.4.0...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2004q4/000186.html][{more}]]
** GnuPG 1.3.93 released (2004-12-14 11:06:45 CET)
The latest and hopefully last release candidate for GnuPG 1.4 is ready
for public consumption. We strongly encourage people to try this release
candidate...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2004q4/000185.html][{more}]]
** sha1sum for MS Windows released (2004-12-09 17:16:22 CET)
In the light of the recently found weaknesses in the MD5 hash function
we won't anymore accompany software announcements with MD5 checksums.
Instead SHA-1 checksums will be given...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2004q4/000184.html][{more}]]
** News available as in RSS 2.0 format (2004-11-25 22:49:58 CET)
As of today, the latest ten news from GnuPG's are available as RSS 2.0
compliant feed. Just point or paste the [[news.en.rss][RSS file]] into
your aggregator.
** GnuPG 1.3.92 released (development) (2004-10-28 14:30:58 CEST)
The latest release from the development branch of GnuPG is ready for
public consumption. This is a branch to create what will extremely soon
become the new stable release of...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2004q4/000183.html][{more}]]
** GPGME 1.0.1 released (2004-10-22 21:27:47 CEST)
We are pleased to announce version 1.0.1 of GnuPG Made Easy, a library
designed to make access to GnuPG easier for...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2004q4/000181.html][{more}]]
** GnuPG 1.3.91 released (development) (2004-10-16 14:46:21 CEST)
The latest release from the development branch of GnuPG is ready for
public consumption. This is a branch to create what will extremely soon
become the new stable release of...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2004q4/000180.html][{more}]]
** Building GnuPG for Win32 using MinGW (2004-10-12)
A new link to Carlo Luciano Bianco's page has been added under the
[[download/index][download section]] . The detailed document is
dedicated to Windows users and explains how to build GnuPG using MinGW.
** GnuPG Subkeys MiniHOWTO (2004-10-11)
With GnuPG and the possibility of having multiple subkeys, you can have
only one key, but still retain the security feature that you do not have
to revoke your primary key (and lose all signatures on it) if the key at
the office is compromised...
[[documentation/howtos.en.html#GnuPG-Subkeys][{more}]]
** GnuPG 1.3.90 released (development) (2004-10-02 15:47:23 CEST)
The latest release from the development branch of GnuPG is ready for
public consumption. This is a branch to create what will...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2004q4/000179.html][{more}]]
** GPGME 1.0.0 released (2004-09-30 18:07:54 CEST)
We are pleased to announce version 1.0.0 of GnuPG Made Easy, a library
designed to make access to GnuPG easier for...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2004q3/000178.html][{more}]]
** GnuPG 1.2.6 released (2004-08-26 12:07:34 CEST)
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.2.6. The GNU Privacy Guard (GnuPG) is...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2004q3/000176.html][{more}]]
** GnuPG 1.2.5 build instruction update (2004-07-27)
Due to a problem with the gettext installation on the build machine a
little annoying bug will disturb...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2004q3/000173.html][{more}]]
** GnuPG 1.2.5 released (2004-07-27)
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.2.5. The GNU Privacy Guard (GnuPG) is...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2004q3/000171.html][{more}]]
** GnuPG 1.2.5 second release candidate (2004-06-16)
We are pleased to announce the availability of the second release
candidate for GnuPG 1.2.5...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2004q2/000169.html][{more}]]
** GnuPG 1.3.6 released (development) (2004-05-22 18:07:54 CEST)
The latest release from the development branch of GnuPG is ready for
public consumption. This is a branch to create what will eventually
become GnuPG 1.4. It will change with greater frequency...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2004q2/000168.html][{more}]]
** First U.S. mirror available (2004-05-06)
We are proud to enlist on our [[download/mirrors.en.html][mirror page]]
the first mirror located in the United States of America. This is the
first tangible effort that we have logged since the rule relaxation by
the U.S. Department of Commerce about
[[http://www.crypto.com/exports/][exporting cryptography]] and we hope
that more mirrors will follow.
** Libgcrypt 1.2.0 released (2004-04-16)
We are pleased to announce the availability of Libgcrypt 1.2.0, which is
the first stable release of this general purpose crypto library...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2004q2/000167.html][{more}]]
** GnuPG 1.2.5 first release candidate (2004-03-29)
We are pleased to announce the availability of the first release
candidate for GnuPG 1.2.5...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2004q1/000166.html][{more}]]
** GnuPG 1.3.5 released (development) (2004-02-26)
The latest release from the development branch of GnuPG is ready for
public consumption. This is a branch to create what will...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2004q1/000165.html][{more}]]
** GnuPG 1.2.4 released (2003-12-24)
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.2.4. The GNU Privacy Guard (GnuPG) is...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2003q4/][{more}]]
** GnuPG 1.3.4 released (development) (2003-11-27)
The latest release from the development branch of GnuPG is ready for
public consumption. This is a branch to create what will...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2003q4/][{more}]]
** GnuPG 1.2.3 patch to remove ElGamal signing keys (2003-11-27)
David Shaw wrote a patch against GnuPG 1.2.3 to disable the ability to
create signatures using the ElGamal sign+encrypt...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2003q4/][{more}]]
** GnuPG's ElGamal signing keys compromised (2003-11-27)
A severe problem with ElGamal sign+encrypt keys has been found. This
leads to a full compromise of the private key. Fortunately...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2003q4/][{more}]]
** Libgcrypt 1.1.44 released (2003-11-01)
We are pleased to announce version 1.1.44 of Libgcrypt, a general
purpose cryptography library based on...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2003q4/][{more}]]
** RISC OS port (2003-10-28)
The [[download][Download section]] now includes a link to Stefan
Bellon's page who ported GnuPG to the RISC OS platform.
** GPA 0.7.0 released (2003-10-22)
We are pleased to announce the release of GPA 0.7.0. GPA is a graphical
frontend for the GNU Privacy Guard...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2003q4/][{more}]]
** GnuPG 1.3.3 released (development) (2003-10-10)
The latest release from the development branch of GnuPG is ready for
public consumption. This is a branch...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2003q4/][{more}]]
** HTTP access to FTP server dismissed (2003-09-22)
Because the HTTP protocol has a couple of problems compared to FTP when
transmitting large files, we decided to dismiss this service for our
server. All the files are thus only available from
[[ftp://ftp.gnupg.org/]] via FTP.
** A Practical Introduction to GPG in Windows (2003-08-22)
The documentation section now contains a
[[documentation/guides.en.html#GPG-Win][new guide]] from Brendan Kidwell
which will hopefully help out Windows users who couldn't get the thing
to work.
** GnuPG one-two-three released (2003-08-22)
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.2.3...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2003q3/][{more}]]
** Libgcrypt 1.1.42 released (2003-07-31)
We are pleased to announce version 1.1.42 of Libgcrypt, a general
purpose cryptography library...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2003q3/][{more}]]
** GnuPG 1.2.3 second release candidate (2003-07-30)
We are pleased to announce the availability of the second release
candidate for GnuPG 1.2.3...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2003q3/][{more}]]
** OpenPGP Smartcards (2003-07-07)
The new OpenPGP smartcards for GnuPG will be shown the first time at the
[[http://www.linuxtag.de/2003/en/index.html][LinuxTag]] , Europe's
largest GNU/Linux exhibition (booth G24).
** GnuPG Keysigning Party HOWTO (2003-06-16)
Documentation section can now count a new entry among its HOWTOs. It is
a valuable source of information for understanding and organizing a
[[documentation/howtos.en.html#GnuPG-Keysigning-Party][GnuPG keysigning party]] .
** GnuPG 1.3.2 released (2003-05-27)
The latest release from the development branch of GnuPG is ready for
public consumption. The more GnuPG-familiar user is encouraged try this
release...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2003q2/000153.html][{more}]]
** Key validity bug in GnuPG 1.2.1 and earlier (2003-05-04)
As part of the development of GnuPG 1.2.2, a bug was discovered in the
key validation code. This bug causes keys with more than one user ID...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2003q2/][{more}]]
** GnuPG 1.2.2 released (2003-05-03)
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.2.2...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2003q2/][{more}]]
** GnuPG.org/(it) 1.0 (2003-04-23)
Version 1.0 of this site's Italian translation has been released. - È
stata rilasciata la versione 1.0 della traduzione italiana di questo
sito.
** New revision of GPH French translation (2003-04-17)
Thanks to Jean-francois for the new French revision of
[[documentation/guides.en.html#gph][The GNU Privacy Handbook]] .
** The No-War banner (2003-04-08)
Recently, a no-war banner has been added to the site. Because not all of
us at GnuPG.org agreed on it, we moved it to the bottom of the page. We
invite you to read more on our mailing-list.
[[https://lists.gnupg.org/pipermail/gpgweb-devel/2003q1/][{more}]]
** GnuPG.org/(es) 0.9 (2003-02-19)
Ha visto la luz la versión 0.9 de la traducción al castellano de este
sitio. - Version 0.9 of this site spanish translation has been released.
** GPA 0.6.1 released (2003-02-03)
We are pleased to announce the release of GPA 0.6.1
[[https://lists.gnupg.org/pipermail/gnupg-announce/2003q1/][{more}]]
** Libgcrypt 1.1.12 released (2003-01-20)
I am pleased to announce a new Beta version of Libgcrypt, GNU's
implementation of basic crypto functions. Libgcrypt is a general...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2003q1/][{more}]]
** GPA 0.6.0 released (2002-12-24)
We are pleased to announce the release of GPA 0.6.0. GPA is a graphical
frontend for the GNU Privacy Guard...
[[gpa-dev/2002-December/index][{more}]]
** GnuPG signature key update and X-Request-PGP (2002-12-23)
The key used to sign GnuPG distributions would expire in a few days. I
have extended the lifetime of this key for another...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2002q4/][{more}]]
** GPGME 0.4.0 released (2002-12-23)
We are pleased to announce version 0.4.0 of GnuPG Made Easy, a library
designed to make access to GnuPG easier for...
[[gpa-dev/2002-December/index][{more}]]
** Libgcrypt 1.1.11 released (2002-12-22)
I am pleased to announce the availability of libgcrypt version 1.1.11.
Libgcrypt is a general purpose cryptographic library based on the code
from GnuPG and...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2002q4/][{more}]]
** gnupg.org 1.1 released (2002-12-15)
New site look has gained several positive critical comments since
revision 1.0 was out, but many bugs were also reported. This revision
tries to fix the most part of them.
** cryptplug 0.3.15 released (2002-12-05)
Due to an error in the configuration system, the previous release had
some problems. This has been fixed and a new version...
[[gpa-dev/2002-December/index][{more}]]
** newpg 0.9.4 released (2002-12-04)
I have just released newpg 0.9.4. NewPG is the S/MIME variant of GnuPG
which does also include the gpg-agent, useful even for...
[[gpa-dev/2002-December/index][{more}]]
** cryptplug 0.3.14 released (2002-12-04)
We have just released the first standalone version of cryptplug.
cryptplug is required for GnuPG and S/MIME support under KDE...
[[gpa-dev/2002-December/index][{more}]]
** gpgme 0.3.14 released (2002-12-04)
We have released gpgme 0.3.14. This version fixes a segv and a race
condition with locales. gpgmeplug is not anymore included...
[[gpa-dev/2002-December/index][{more}]]
** New look-and-feel site released to the public (2002-12-01)
After about four months of WML coding (well, summer was on the way ;-),
first revision of the new site look-and-feel was released today. Site is
available in english only for now.
** OpenCDK 0.3.3 (2002-11-25)
This is the first public announcement for OpenCDK. It is a library to
provide some basic parts of the OpenPGP Message Format...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2002q4/][{more}]]
** Pyme -- Python OO interface to GPGME (2002-11-20)
Today I am announcing the first release of Pyme, the brand-new Python
bindings for GPGME....
[[https://lists.gnupg.org/pipermail/gnupg-announce/2002q4/][{more}]]
** GnuPG 1.3.1 released (development) (2002-11-12)
The latest release from the development branch of GnuPG is ready for
public consumption. This is a branch to create what will...
** GPGRemail v0.1 initial announcement (2002-11-06)
GPGRemail is a minimalistic mailinglist software, meant for small,
private, mailinglists that require strong cryptography via...
** RPMs (2002-10-28)
I'm currently uploading RPMs packages for gnupg 1.2.1. At this moment
I've uploaded src and mdk 9.0 packages. The latter...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2002q4/][{more}]]
** GnuPG 1.2.1 Windows update released (2002-10-26)
Due to a bug in the recent mingw32/cpd toolkit the latest GnuPG binary
for Windows did not work on Windows NT. I have build...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2002q4/][{more}]]
** GnuPG 1.2.1 has been released (2002-10-25)
Please see this [[download/release_notes.en.html#news-2002-10-25][list
of changes]] and then go to the [[download/index.en.html][download
instructions]] .
** GnuPG 1.3.0 released (development) (2002-10-18)
The first release from the new development branch of GnuPG is ready for
public consumption. This is a branch to create what...
[[https://lists.gnupg.org/pipermail/gnupg-announce/2002q4/][{more}]]
** GnuPG 1.2.0 released (2002-09-21)
Far too many enhancements to be listed here, please see the
[[https://lists.gnupg.org/pipermail/gnupg-announce/2002q3/000252.html][announcement mail]] .
** New site (2002-06-20)
Developmenent of the site new look and feel has started.
** ftp.gnupg.org HTTP access (2002-05-08)
[[http://ftp.gnupg.org][ftp.gnupg.org]] can now also be accessed by
HTTP.
** GnuPG 1.0.7 released (2002-04-29)
Far too many enhancements to be listed here, please see the
[[https://lists.gnupg.org/pipermail/gnupg-announce/2002q2/000251.html][announcement mail]] .
** GPA 0.4.3 released (2002-01-14)
[[software/gpa/index.en.html][GPA]] 0.4.3 has been released.
** GPA pages (2001-11-15)
[[software/gpa/index.en.html][GPA pages]] reflect latest released version (gpa-0.4.2) now.
** GnuPG 1.0.6 released (2001-05-29)
See the [[download/release_notes.en.html#news-2001-05-29][release note]].
** GnuPG 1.0.5 for W32 released (2001-05-02)
Released GnuPG 1.0.5 binary for W32.
** GnuPG 1.0.5 released (2001-04-29)
- The semantics of --verify have changed.
- Corrected hash calculation for input data larger than 512M.
- Large File Support is now working.
- A bunch of new options and commands.
- Keyserver support for the W32 version.
- Better handling of key expiration and subkeys.
- Estonian and Turkish translation.
- The usual fixes and other enhancements.
** New CVS access instructions (2001-04-18)
Changed the instructions for CVS access and add a list of available
modules.
** GnuPG Tools (2001-04-03)
Add a new webpage about GnuPG tools.
** News about gnupg.de (2001-03-28)
News flash about [[http://www.gnupg.de][www.gnupg.de]] .
** Link to Phil Zimmermann (2001-03-24)
Add a link to [[http://web.mit.edu/~prz][Phil Zimmermann]] 's homepage.
** New page about GPGME (2001-02-22)
Add a page about [[software/gpgme/index.en.html][GPGME]] .
** Patch for GnuPG 1.0.4 released (2000-11-30)
Fixed a serious bug which could lead to false positives when checking
detached signatures.
** New web design (2000-10-26)
New design of these web pages.
** GnuPG 1.0.4 W32 released (2000-10-23)
Pre-compiled version of [[download/index.en.html][GnuPG 1.0.4]] for
Windows released.
** GnuPG 1.0.4 (2000-10-17)
- Fixed a serious bug which could lead to false signature verification
results when more than one signature is fed to gpg.
- New utility gpgv which is a stripped down version of gpg to be used
to verify signatures against a list of trusted keys.
- Rijndael (AES) is now supported.
** German GPH (2000-10-06)
Put the [[documentation/guides.en.html#gph][German version]] of the GPH
online.
** Secure Telephony (2000-09-27)
Add a link about secure telephony and a pointer to a Japanese
translation of RFC2440.
** GnuPG 1.0.3 released (2000-09-20)
- RSA support.
- Supports the new MDC encryption packet.
- Default options changed for better compatibility with PGP 7.
- The usual fixes and other enhancements.
** FAQ (2000-09-06)
Add a [[documentation/faqs.en.html][FAQ]] .
** Site improvements (2000-08-28)
Add a short menu to the top of the docs page. Add a note about the PGP
ARR problem.
** Links to GPH (2000-08-08)
Put links to the GPH into the doc webpage.
** Italian web site (2000-08-02)
Italian translation of the web pages.
** GnuPG 1.0.2 released (2000-07-12)
A lot of fixes and enhancements.
** Pages about PGA (2000-06-29)
Add some pages about the [[software/gpa/][GPA]].
** Two new supported OSes (2000-03-20)
Add 2 OSes to the list of supported systems.
** CVS access (2000-03-15)
[[https://cvs.gnupg.org/][cvs.gnupg.org]] provides browsable access to
the CVS tree of GnuPG and related projects.
** GnuPG 1.0.1 released (1999-12-16)
Bug fixes and small enhancements.
** GnuPG 1.0.0 released (1999-09-07)
Released the first production version.
** GnuPG 0.9.11 released (1999-09-03)
Some more fixes and cleanups.
** GnuPG 0.9.10 released (1999-08-04)
Minor bug fixes.
** GnuPG 0.9.9 released (1999-07-23)
- Yet another chunk of options.
- More bug fixes.
** GnuPG 0.9.8 released (1999-06-26)
- A couple of new options.
- Yet another workaround for PGP2.
- Other bug fixes.
** GnuPG 0.9.7 released (1999-05-23)
- Workarounds for a couple of PGP2 bugs.
- Other bug fixes.
** GnuPG 0.9.6 released (1999-05-06)
- Bug fixes.
- Subkey and signature revocations.
** GnuPG 0.9.5 released (1999-03-20)
- Bug fixes.
- --recv-keys command
** GnuPG 0.9.4 released (1999-03-08)
Bug fixes.
** GnuPG 0.9.3 released (1999-02-19)
- Bug fixes.
- Some new options.
** GnuPG 0.9.2 released (1999-01-20)
- Bug fixes.
- HKP keyserver support.
** GnuPG 0.9.1 released (1999-01-01)
- Fixed some serious bugs.
- Some internal redesign.
- Polish language support.
- Setup a anonymous rsync server.
** GnuPG 0.9.0 released (1998-12-23)
- Option to dash-escape "From" in clear text messages.
- Better support for unices without /dev/random.
- Fixed some bugs.
** GnuPG 0.4.5 released (1998-12-08)
- Brazilian translation.
- Improved key import.
- Loadable random gathering stuff.
- Files are now locked during updates.
** GnuPG 0.4.4 released (1998-11-20)
- Spanish translation.
- Fixed the way expiration dates are stored.
- Key validation is now much faster and some more bugs fixed.
- New feature to support signed patch files.
** GnuPG 0.4.3 released (1998-11-08)
- Russian translation.
- Now lists all matching names.
- Experimental support for keyrings store in GDBM files.
- Many bug fixes.
** GnuPG 0.4.1 released (1998-10-07)
- Fixed a couple of bugs and add some more features.
- Checked OpenPGP compliance.
- PGP 5 passphrase are now working.
** GnuPG 0.4.0 released (1998-09-18)
- Fixed a serious Bug in 0.3.5.
- Added 3DES.
** GnuPG 0.3.5 released (1998-09-14)
- Do not use this version!
- Anonymous enciphered messages.
- Building in another directory now work better.
- Blowfish weak key detection mechanism.
** GnuPG 0.3.4 released (1998-08-11)
Relased revision 0.3.4.
** GnuPG 0.3.3 released (1998-08-08)
- Alternate user IDs.
- A menu to sign, add, remove user ids and other tasks.
- [[http://www.counterpane.com/twofish.html][Twofish]] as a new experimental cipher algorithm.
- Ability to run as a coprocess; this is nice for frontends.
** GnuPG 0.3.2 released (1998-07-09)
Bug fixes.
** GnuPG 0.3.1 released (1998-07-06)
- Bug fixes.
- More in compliance with OpenPGP.
** GnuPG 0.3.0 released (1998-06-25)
- Major enhancements.
- More complete v4 key support: Preferences and expiration time is set
into the self signature.
- Key generation defaults to DSA/ElGamal keys, so that new keys are
interoperable with pgp5.
- Support for dynamic loading of new algorithms.
** GnuPG 0.2.19 released (1998-05-29)
- Tiger has now the OpenPGP assigned number 6. Because the OID has
changed, old signatures using this algorithm can't be verified.
- GnuPG now encrypts the compressed packed and not any longer in the
reverse order; anyway it can decrypt both versions.
- =--add-key= works and you are now able to generate subkeys.
- It is now possible to generate ElGamal keys in v4 packets to create
valid OpenPGP keys.
- Some new features for better integration into MUAs.
** GnuPG 0.2.18 released (1998-05-15)
- Add key generation for DSA and v4 signatures.
- Fixed a small bug in the key generation.
- New option =--compress-algo 1= to allow the creation of compressed
messages which are readable by PGP.
** GnuPG 0.2.17 released (1998-05-04)
- More stuff for OpenPGP: Blowfish is now type 20, comment packets
moved to a private type, packet type 3 now prepends conventional
encryption packets.
- Fixed a passphrase bug and some others.
** GnuPG 0.2.16 released (1998-04-28)
- Experimental support for TIGER/192.
- Standard cipher is now Blowfish with 128 bit key in OpenPGP's CFB
mode.
** GnuPG 0.2.15 released (1998-04-09)
- Fixed a bug with the old checksum calculation for secret keys.
- CAST5 works (using PGP's strange CFB mode).
** GnuPG 0.0.0 released (1997-12-20)
First release.
diff --git a/web/swdb.mac b/web/swdb.mac
index 1ae47f2..afb3207 100644
--- a/web/swdb.mac
+++ b/web/swdb.mac
@@ -1,227 +1,227 @@
# Version information
# Please run make in this directory after changing this file.
#
# Primary FTP server base directory
#
#+macro: ftp_base ftp://ftp.gnupg.org/gcrypt
#+macro: ftp_loc_base /ftp/gcrypt
#
# GnuPG-2.2
#
-#+macro: gnupg22_ver 2.2.4
-#+macro: gnupg22_date 2017-12-20
-#+macro: gnupg22_size 6417k
-#+macro: gnupg22_sha1 732266e8888c6f41c084d043c7a0058332ff3580
-#+macro: gnupg22_sha2 401a3e64780fdfa6d7670de0880aa5c9d589b3db7a7098979d7606cec546f2ec
+#+macro: gnupg22_ver 2.2.5
+#+macro: gnupg22_date 2018-02-22
+#+macro: gnupg22_size 6430k
+#+macro: gnupg22_sha1 9dec110397e460b3950943e18f5873a4f277f216
+#+macro: gnupg22_sha2 3fa189a32d4fb62147874eb1389047c267d9ba088f57ab521cb0df46f08aef57
#+macro: gnupg22_branch STABLE-BRANCH-2-2
-#+macro: gnupg22_w32_ver 2.2.4_20171220
-#+macro: gnupg22_w32_date 2017-12-20
-#+macro: gnupg22_w32_size 3817k
-#+macro: gnupg22_w32_sha1 d06a1413fd901c51eba14164ddb28d99ab9f84df
-#+macro: gnupg22_w32_sha2 2030f00548ec175cac4996a8128ed71393c156429d95f3e6c2f53194b2f4d885
+#+macro: gnupg22_w32_ver 2.2.5_20180222
+#+macro: gnupg22_w32_date 2018-02-22
+#+macro: gnupg22_w32_size 3819k
+#+macro: gnupg22_w32_sha1 080f801e833c7a9e0441d55cd19d4bdb5bb261f9
+#+macro: gnupg22_w32_sha2 9fea4add738a373b3c1a304f74eec2d24a8f5fe7ccdf1d8ee090d99de8f51257
# temporary keep it as "gnupg21". In the future we will use the name of
# the stable branch even for the development versions.
-#+macro: gnupg21_ver 2.2.4
-#+macro: gnupg21_date 2017-12-20
-#+macro: gnupg21_size 6417k
-#+macro: gnupg21_sha1 732266e8888c6f41c084d043c7a0058332ff3580
-#+macro: gnupg21_sha2 401a3e64780fdfa6d7670de0880aa5c9d589b3db7a7098979d7606cec546f2ec
+#+macro: gnupg21_ver 2.2.5
+#+macro: gnupg21_date 2018-02-22
+#+macro: gnupg21_size 6430k
+#+macro: gnupg21_sha1 9dec110397e460b3950943e18f5873a4f277f216
+#+macro: gnupg21_sha2 3fa189a32d4fb62147874eb1389047c267d9ba088f57ab521cb0df46f08aef57
#+macro: gnupg21_branch STABLE-BRANCH-2-2
-#+macro: gnupg21_w32_ver 2.2.4_20171220
-#+macro: gnupg21_w32_date 2017-12-20
-#+macro: gnupg21_w32_size 3817k
-#+macro: gnupg21_w32_sha1 d06a1413fd901c51eba14164ddb28d99ab9f84df
-#+macro: gnupg21_w32_sha2 2030f00548ec175cac4996a8128ed71393c156429d95f3e6c2f53194b2f4d885
+#+macro: gnupg21_w32_ver 2.2.5_20180222
+#+macro: gnupg21_w32_date 2018-02-22
+#+macro: gnupg21_w32_size 3819k
+#+macro: gnupg21_w32_sha1 080f801e833c7a9e0441d55cd19d4bdb5bb261f9
+#+macro: gnupg21_w32_sha2 9fea4add738a373b3c1a304f74eec2d24a8f5fe7ccdf1d8ee090d99de8f51257
#
# GnuPG 2.0 (end-of-life)
#
#+macro: gnupg20_ver 2.0.31
#+macro: gnupg20_date 2017-12-29
#+macro: gnupg20_size 4324k
#+macro: gnupg20_sha1 a7d5021a6a39dd67942e00a1239e37063edb00f0
#+macro: gnupg20_sha2 095558cfbba52fba582963e97b0c016889570b4712d6b871abeef2cf93e62293
#+macro: gnupg20_branch STABLE-BRANCH-2-0
#
# GnuPG-1
#
#+macro: gnupg1_ver 1.4.22
#+macro: gnupg1_date 2017-07-19
#+macro: gnupg1_size 3658k
#+macro: gnupg1_sha1 4bad84fba712626cbbd5adf20988788028c5a5a6
#+macro: gnupg1_sha2 9594a24bec63a21568424242e3f198b9d9828dea5ff0c335e47b06f835f930b4
#
#+macro: gnupg1_w32cli_ver 1.4.22
#+macro: gnupg1_w32cli_size 2372k
#+macro: gnupg1_w32cli_sha1 27b8069872d6d2b271222ffb9322dbd6197b0b89
#
# Gpg4win
#
#+macro: gpg4win_ver 3.0.3
#+macro: gpg4win_date 2018-01-12
#+macro: gpg4win_src_size 5226k
#+macro: gpg4win_src_sha1 4be455a6e8176054ce940ae68890e8aa82a99137
#+macro: gpg4win_src_sha2 fda270694eca7f4a6767e3a239d15d1166313c397cf83d6d06ad962a7a13717b
#+macro: gpg4win_exe_size 26357k
#+macro: gpg4win_exe_sha1 e901af858a964192cec891cdbae76ca6789d741c
#+macro: gpg4win_exe_sha2 477f56212ee60cc74e0c5e5cc526cec52a069abff485c89c2d57d1b4b6a54971
#+macro: gpg4win_isrc_size 220342k
#+macro: gpg4win_isrc_sha1 cb259311fe133017847981f31cb9b1fba6e2e456
#+macro: gpg4win_isrc_sha2 41cb2a6d17ab0b0a0bd45a06e4dcc421191297e928a23afdf7ff8a349dedc59e
#
# GPA
#
#+macro: gpa_ver 0.9.10
#+macro: gpa_date 2016-11-19
#+macro: gpa_size 745k
#+macro: gpa_sha1 c629348725c1bf5dafd57f8a70187dc89815ce60
#+macro: gpa_sha2 c3b9cc36fd9916e83524930f99df13b1d5f601f4c0168cb9f5d81422e282b727
#
# PINENTRY
#
#+macro: pinentry_ver 1.1.0
#+macro: pinentry_date 2017-12-03
#+macro: pinentry_size 456k
#+macro: pinentry_sha1 693bdf9f48dfb3e040d92f50b1bb464e268b9fb0
#+macro: pinentry_sha2 68076686fa724a290ea49cdf0d1c0c1500907d1b759a3bcbfbec0293e8f56570
#
# GPGME
#
#+macro: gpgme_ver 1.10.0
#+macro: gpgme_date 2017-12-12
#+macro: gpgme_size 1338k
#+macro: gpgme_sha1 77d3390887da25ed70b7ac04392360efbdca501f
#+macro: gpgme_sha2 1a8fed1197c3b99c35f403066bb344a26224d292afc048cfdfc4ccd5690a0693
#
# LIBGCRYPT
#
#+macro: libgcrypt_ver 1.8.2
#+macro: libgcrypt_date 2017-12-13
#+macro: libgcrypt_size 2897k
#+macro: libgcrypt_sha1 ab8aae5d7a68f8e0988f90e11e7f6a4805af5c8d
#+macro: libgcrypt_sha2 c8064cae7558144b13ef0eb87093412380efa16c4ee30ad12ecb54886a524c07
#
# LIBKSBA
#
#+macro: libksba_ver 1.3.5
#+macro: libksba_date 2016-08-22
#+macro: libksba_size 606k
#+macro: libksba_sha1 a98385734a0c3f5b713198e8d6e6e4aeb0b76fde
#+macro: libksba_sha2 41444fd7a6ff73a79ad9728f985e71c9ba8cd3e5e53358e70d5f066d35c1a340
#
# DirMngr (not any longer needed)
#
#+macro: dirmngr_ver 1.1.1
#+macro: dirmngr_date 2013-04-26
#+macro: dirmngr_size 554k
#+macro: dirmngr_sha1 e708d4aa5ce852f4de3f4b58f4e4f221f5e5c690
#
# LIBGPG-ERROR
#
#+macro: libgpg_error_ver 1.27
#+macro: libgpg_error_date 2017-02-28
#+macro: libgpg_error_size 794k
#+macro: libgpg_error_sha1 a428758999ff573e62d06892e3d2c0b0f335787c
#+macro: libgpg_error_sha2 4f93aac6fecb7da2b92871bb9ee33032be6a87b174f54abf8ddf0911a22d29d2
#
# LIBASSUAN
#
#+macro: libassuan_ver 2.5.1
#+macro: libassuan_date 2017-12-07
#+macro: libassuan_size 551k
#+macro: libassuan_sha1 c8432695bf1daa914a92f51e911881ed93d50604
#+macro: libassuan_sha2 47f96c37b4f2aac289f0bc1bacfa8bd8b4b209a488d3d15e2229cb6cc9b26449
#
# NTBTLS
#
#+macro: ntbtls_ver 0.1.2
#+macro: ntbtls_date 2017-09-19
#+macro: ntbtls_size 334k
#+macro: ntbtls_sha1 05cf57cd8400b338b94bdce7287397c24315ac49
#+macro: ntbtls_sha2 8240db84e50c2351b19eb8064bdfd4d25e3c157d37875c62e335df237d7bdce7
#
# nPth
#
#+macro: npth_ver 1.5
#+macro: npth_date 2017-06-02
#+macro: npth_size 292k
#+macro: npth_sha1 93ddf1a3bdbca00fb4cf811498094ca61bbb8ee1
#+macro: npth_sha2 294a690c1f537b92ed829d867bee537e46be93fbd60b16c04630fbbfcd9db3c2
#
# GpgEX
#
#+macro: gpgex_ver 1.0.4
#+macro: gpgex_date 2016-03-30
#+macro: gpgex_size 286k
#+macro: gpgex_sha1 a1521fd86b6a1c5d5865d864e5700e98f4e99dcb
#+macro: gpgex_sha2 aea2232d026219072491f1bf5b2f189a15552f66377ff4dd3b11c0f069379206
#
# GpgOL
#
#+macro: gpgol_ver 2.0.5
#+macro: gpgol_date 2017-12-08
#+macro: gpgol_size 750k
#+macro: gpgol_sha1 2f7eb7453ad5c6e811823be5348eec4c78f97695
#+macro: gpgol_sha2 8fa5d4d13edfb344ec75a0e9dce3e633e6ce81e92cd388b73e2d34a14c78d46e
#
# ADNS
#
#+macro: adns_ver 1.4-g10-7
#+macro: adns_date 2015-11-20
#+macro: adns_sha1 d2e089d98d3faed6cad009477cc0bc030b35c646
#
# zlib (mirrored at our server)
#
#+macro: zlib_ver 1.2.8
#+macro: zlib_sha1_gz a4d316c404ff54ca545ea71a27af7dbc29817088
#
# bzip2 (mirrored and stripped down version)
#
#+macro: bzip2_ver 1.0.6-g10
#+macro: bzip2_sha1_gz 6e38be3377340a21a1f13ff84b5e6adce97cd1d4
#
# SQLite (mirrored at our server)
#
#+macro: sqlite_ver 3120200
#+macro: sqlite_sha1_gz b43c2e7238e54c50b95fbbd85c48792f4f39af8c
# --- end of swdb.mac ---