*/*: Chase security/libassuan shlib bump

security/gnupg: Update to 2.4.5

ReleaseNotes:	https://lists.gnupg.org/pipermail/gnupg-announce/2024q1/000482.html
PR:		278605
Approved by:	maintainer timeout

security/gnupg: Use gpgrt-config for configure

Use gpgrt-config in the configure stage over the old individual
*-config scripts from the various gnupg-related libraries (e.g:
gpg-error-config, libassuan-config, ksba-config). Upstream has
prefered this method since version 2.3.0 released 2021-04-07 and
the old scripts are now starting to be phased-out.

This prepares for devel/npth >= 1.7 which no longer installs
npth-config by default, so gpgrt-config must be used to get its
configuration details.

Approved by:	portmgr (blanket)

security/gnupg: Fix postexec/postunexec dealing with manpages

Approved by:	portmgr (blanket)

security/gnupg: Update to 2.4.4

Changelog:	https://dev.gnupg.org/T6578
Sponsored by:	The FreeBSD Foundation

Approved by:	adridg (maintainer)
Differential Revision:	https://reviews.freebsd.org/D43787

security/gnupg: Moved man to share/man

Approved by:    portmgr (blanket)

security/gnupg: Fix plist

Reported by:	des
Approved by:	portmgr blanket
Fixes:		06227fb64bf2 security/gnupg: Create symlink for manpage

security/gnupg: Create symlink for manpage

When security/gnupg1 isn't installed, ${PREFIX}/bin/gpg symlink is
created whose target is 'gpg2'. It means gpg2 can also be invoked as
'gpg'. And under such situation it is convenient for user if gpg2(1)
man page can also be accessed as gpg(1). So create
${PREFIX}/man/man1/gpg.1.gz symlink whose target is 'gpg2.1.gz'.

PR:		272519
Approved by:	maintainer timeout

Revert "security/gnupg: Fix dirmngr crash caused by gettext 0.22"

This reverts commit 7fa24cff0d8a99e5d44839d4b358fafaf69cffbe.

The problem has been fixed in libintl in fb889ca82944.

PR:		272472

security/gnupg: Fix dirmngr crash caused by gettext 0.22

Link the threading library after libgpg-error (and libgcrypt, which also
links to libgpg-error) so the threading library is initialised before
libgpg-error.  The initialisation function of libgpg-error calls gettext
functions that call threading functions (mutex locking).

PR:		272472
Tested by:	yasu

security/gnupg: Update to 2.4.3

2.4.3: https://dev.gnupg.org/T6509
2.4.2: https://dev.gnupg.org/T6506
2.4.1: https://dev.gnupg.org/T6454
2.4.0: https://dev.gnupg.org/T6303

PR:		272083
Approved by:	maintainer timeout (3 weeks)

Mk/**ldap.mk: Convert USE_LDAP to USES=ldap

Convert the USE_LDAP=yes to USES=ldap and adds the following features:

- Adds the argument USES=ldap:server to add openldap2{4|5|6}-server as
  RUN_DEPENDS
- Adds the argument USES=ldap<version> and replaces WANT_OPENLDAP_VER
- Adds OPENLDAP versions in bsd.default-versions.mk
- Adds USE_OPENLDAP/WANT_OPENLDAP_VER in Mk/bsd.sanity.mk
- Changes consumers to use the features

Reviewed by:	delphij
Approved by:	portmgr
Differential Revision: https://reviews.freebsd.org/D38233

security/gnupg: Update to 2.3.8

Changelog:
https://lists.gnupg.org/pipermail/gnupg-announce/2022q4/000476.html

Some additional changes to submitted patch:
- Change PORTVERSION to DISTVERSION
- Generate patch using "make makepatch"
- Remove obsolete configure switch

PR:		267152
Reviewed by:	adridg (maintainer)
Tested by:	Dennis Clarke <dclarke@blastwave.org>

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

security/gnupg: remove unnecessary pkg-message

There were installation instructions that dated from ~2017
which are no longer relevant after a fix was applied upstream.
An IPv4 host connecting to a dual-stack hks server now gets a meaningful
errno and retries the connection (as IPv4 only).

Reported by:	Pau Amma
PR:		262881

Fix CONFLICTS entries of multiple ports

There have been lots of missing CONFLICTS_INSTALL entries, either
because conflicting ports were added without updating existing ports,
due to name changes of generated packages, due to mis-understanding
the format and semantics of the conflicts entries, or just due to
typoes in package names.

This patch is the result of a comparison of all files contained in
the official packages with each other. This comparison was based on
packages built with default options and may therefore have missed
further conflicts with optionally installed files.

Where possible, version numbers in conflicts entries have been
generalized, some times taking advantage of the fact that a port

security/gnupg: fix table / enum mismatch

PR259775 reports that (auto)configuration behaves weirdly.
This is caused by a mismatch between an enum in the code
and a table that expects to match the enum values. When
BUILD_WITH_TPM2D is off (the default; I have not looked if
it can even be turned on in ports) one table entry is

Patch also submitted upstream.

PR:		259775
Reported by:	O. Hartmann
MFH:		2021Q3

security/gnupg{,1}: Transfer maintainership to adridg

sysutils/gnupg: Fix running without procfs

*/*: Remove redundant '-[0-9]*' from CONFLICTS

The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").

Many CONFLICTS definitions used patterns like "bash-[0-9]*" to filter
for the bash package in any version. But that pattern is functionally
identical with just "bash".

Approved by:	portmgr (blanket)

security/gnupg: Update to 2.3.3

Changes:
 * agent: Fix segv in GET_PASSPHRASE (regression).  [#5577]

  * dirmngr: Fix Let's Encrypt certificate chain validation.  [#5639]

  * gpg: Change default and maximum AEAD chunk size to 4 MiB.
    [ad3dabc9fb]

  * gpg: Print a warning when importing a bad cv25519 secret key.
    [#5464]

  * gpg: Fix --list-packets for undecryptable AEAD packets.  [#5584]

security/gnupg: Update to 2.3.2

Changes:
  * gpg: Allow fingerprint based lookup with --locate-external-key.
    [ec36eca08c]

  * gpg: Allow decryption w/o public key but with correct card
    inserted.  [50293ec2eb]

  * gpg: Auto import keys specified with --trusted-keys.  [100037ac0f]

  * gpg: Do not use import-clean for LDAP keyserver imports.  [#5387]

  * gpg: Fix mailbox based search via AKL keyserver method.  [4fcfac6feb]

security/gnupg: Update to 2.3.1

security/gnupg: Update to 2.3.0

Changes:
  * A new experimental key database daemon is provided.  To enable it
    put "use-keyboxd" into gpg.conf and gpgsm.conf.  Keys are stored
    in a SQLite database and make key lookup much faster.

  * New tool gpg-card as a flexible frontend for all types of
    supported smartcards.

  * New option --chuid for gpg, gpgsm, gpgconf, gpg-card, and
    gpg-connect-agent.

  * The gpg-wks-client tool is now installed under bin; a wrapper for
    its old location at libexec is also installed.

One more small cleanup, forgotten yesterday.
Reported by:	lwhsu

Remove # $FreeBSD$ from Makefiles.

security/gnupg: Update to 2.2.27

 * gpg: Fix regression in 2.2.24 for gnupg_remove function under
   Windows.  [#5230]

 * gpgconf: Fix case with neither local nor global gpg.conf.  [9f37d3e6f3]

 * gpgconf: Fix description of two new options.  [#5221]

 * Build Windows installer without timestamps.  Note that the
   Authenticode signatures still carry a timestamp.

  Release-info: https://dev.gnupg.org/T5234

security/gnupg: Update to 2.2.26

Note that this release removes bin/symcryptrun which had essentially no
expected current use-case.

 * gpg: New AKL method "ntds".
 * gpg: Fix --trusted-key with fingerprint arg.
 * scd: Fix writing of ECC keys to an OpenPGP card.  [#5163]
 * scd: Make an USB error fix specific to SPR532 readers.  [#5167]
 * dirmngr: With new LDAP keyservers store the new attributes.  Never
   store the useless pgpSignerID.  Fix a long standing bug storing
   some keys on an ldap server.
 * dirmngr: Support the new Active Direcory LDAP schema for
   keyservers.
 * dirmngr: Allow LDAP OpenPGP searches via fingerprint.
 * dirmngr: Do not block other threads during keyserver LDAP calls.
 * Support global configuration files.  [#4788]
 * Fix the iconv fallback handling to UTF-8.  [#5038]
 Release-info: https://dev.gnupg.org/T5153

security/gnupg: Update to 2.2.25

  * scd: Fix regression in 2.2.24 requiring gpg --card-status before
    signing or decrypting.  [#5065]

  * gpgsm: Using Libksba 1.5.0 signatures with a rarely used
    combination of attributes can now be verified.  [#5146]

  Release-info: https://dev.gnupg.org/T5140

security/gnupg: Update to 2.2.24

  * Allow Unicode file names on Windows almost everywhere.  Note that
    it is still not possible to use Unicode strings on the command
    line.  This change also fixes a regression in 2.2.22 related to
    non-ascii file names.  [#5098]

  * Fix localized time printing on Windows.  [#5073]

  * gpg: New command --quick-revoke-sig.  [#5093]

  * gpg: Do not use weak digest algos if selected by recipient
    preference during sign+encrypt.  [4c181d51a6]

  * gpg: Switch to AES256 for symmetric encryption in de-vs mode.

security/gnupg: Update to 2.2.23

Importing an OpenPGP key having a preference list for AEAD algorithms
will lead to an array overflow and thus often to a crash or other
undefined behaviour.

Importing an arbitrary key can often easily be triggered by an attacker
and thus triggering this bug.  Exploiting the bug aside from crashes is
not trivial but likely possible for a dedicated attacker.  The major
hurdle for an attacker is that only every second byte is under their
control with every first byte having a fixed value of 0x04.

Software distribution verification should not be affected by this bug
because such a system uses a curated list of keys.

MFH:		2020Q3
Security:	CVE-2020-25125

security/gnupg: Update to 2.2.22

Also, sort plist. The new gpgsplit binary is getting installed as
gpgsplit2 to avoid a conflict with security/gnupg1.

Noteworthy changes in version 2.2.22
====================================

  * gpg: Change the default key algorithm to rsa3072.

  * gpg: Add regular expression support for Trust Signatures on all
    platforms.  [#4843]

  * gpg: Fix regression in 2.2.21 with non-default --passphrase-repeat
    option.  [#4991]

Unmute some build commands

gnupg: Update to 2.2.21

 * gpg: Improve symmetric decryption speed by about 25%.
   See commit 144b95cc9d.

 * gpg: Support decryption of AEAD encrypted data packets.

 * gpg: Add option --no-include-key-block. [#4856]

 * gpg: Allow for extra padding in ECDH.  [#4908]

 * gpg: Only a single pinentry is shown for symmetric encryption if
   the pinentry supports this.  [#4971]

 * gpg: Print a note if no keys are given to --delete-key.  [#4959]

gnupg: Update to 2.2.20

Noteworthy changes in version 2.2.20
====================================

  * Protect the error counter against overflow to guarantee that the
    tools can't be tricked into returning success after an error.

  * gpg: Make really sure that --verify-files always returns an error.

  * gpg: Fix key listing --with-secret if a pattern is given.  [#4061]

  * gpg: Fix detection of certain keys used as default-key.  [#4810]

  * gpg: Fix default-key selection when a card is available.  [#4850]

gnupg: Update to 2.2.19

  * gpg: Fix double free when decrypting for hidden recipients.
    Regression in 2.2.18.  [#4762].

  * gpg: Use auto-key-locate for encryption even for mail addressed
    given with angle brackets.  [#4726]

  * gpgsm: Add special case for certain expired intermediate
    certificates.  [#4696]

  Release-info: https://dev.gnupg.org/T4768

gnupg: Update to 2.2.18

  * gpg: Changed the way keys are detected on a smartcards; this
    allows the use of non-OpenPGP cards.  In the case of a not very
    likely regression the new option --use-only-openpgp-card is
    available.  [#4681]

  * gpg: The commands --full-gen-key and --quick-gen-key now allow
    direct key generation from supported cards.  [#4681]

  * gpg: Prepare against chosen-prefix SHA-1 collisions in key
    signatures.  This change removes all SHA-1 based key signature
    newer than 2019-01-19 from the web-of-trust.  Note that this
    includes all key signature created with dsa1024 keys.  The new
    option --allow-weak-key-signatues can be used to override the new

security/gnupg: add the --shared-access option to scdaemon

gnupg's scdaemon opens smart cards in exclusive mode, which prevents other
applications (such as PKCS#11 libraries) from concurrently accessing the
card). Upstream refuses to fix the problem. This commit adds a
--shared-access option to scdaemon. When enabled, scdaemon will access the
smart card in shared mode, playing nicely with other applications. The
default behavior is unchanged.

See Also:
https://github.com/GPGTools/MacGPG2/commit/d6cb8039a0cdc74b9bdd89a3dfa93248aa2c4100
https://dev.gnupg.org/T3267
https://dev.gnupg.org/D320
https://github.com/OpenSC/OpenSC/issues/953

Reviewed by:	adamw
Approved by:	adamw (maintainer)
Obtained-from:	GPGTools
Sponsored by:	Axcient
Differential Revision:	https://reviews.freebsd.org/D22473

gnupg: Fix building on 11.3

Submitted by:	asomers
Differential Revision:	https://reviews.freebsd.org/D22492

security/gnupg: fix build, texinfo is required for man pages too

security/gnupg: rebuild man pages on every build

gnupg ships its man pages as texinfo files, precompiled into info files.
This change causes make to rebuild them every time.  There are two reasons:

* Rebuilding them automatically corrects several Linuxisms in paths (e.g.
  /etc => /usr/local/etc).

* Rebuilding them is a neccessary precondition for making any local changes
  that will affect the content of the man pages, which I intend to do in a
  future commit.

Reviewed by:	adamw
Approved by:	adamw (maintainer)
Sponsored by:	Axcient
Differential Revision:	https://reviews.freebsd.org/D22471

gnupg: Spell "_DESC" correctly. It was missing 5 characters.

gnupg: Add WKS_SERVER option

Requested by:	koobs

gnupg: enable the WKS server

Cristoph Lukas asked me why the WKS server was disabled, and I have
no idea. It was added r462573, and that commit message and associated
bug report don't list why --disable-wks-tools was added. (Folks,
please use commit messages for writing, you know, messages.)

We've been installing the gpg-wks-server manpage, so this commit
enables the WKS server and installs the binary, and bumps PORTREVISION
for it.

While here, sort the plist.

Convert to UCL & cleanup pkg-message (categories s)

Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.

PR:		238330

gnupg: Update to 2.2.17, with security fixes

 * gpg: Ignore all key-signatures received from keyservers.  This
   change is required to mitigate a DoS due to keys flooded with
   faked key-signatures.  The old behaviour can be achieved by adding
     keyserver-options no-self-sigs-only,no-import-clean
   to your gpg.conf.  [#4607]

 * gpg: If an imported keyblocks is too large to be stored in the
   keybox (pubring.kbx) do not error out but fallback to an import
   using the options "self-sigs-only,import-clean".  [#4591]

 * gpg: New command --locate-external-key which can be used to
   refresh keys from the Web Key Directory or via other methods
   configured with --auto-key-locate.

Update gnupg to 2.2.16

Update devel/readline to 8.0

- Bump PORTREVISION of dependent ports for shlib change

Changes:	https://tiswww.case.edu/php/chet/readline/CHANGES
PR:		236156
Exp-run by:	antoine

Update gnupg to 2.2.15

  * sm: Fix --logger-fd and --status-fd on Windows for non-standard
    file descriptors.

  * sm: Allow decryption even if expired keys are configured.  [#4431]

  * agent: Change command KEYINFO to print ssh fingerprints with other
    hash algos.

  * dirmngr: Fix build problems on Solaris due to the use of reserved
    symbol names.  [#4420]

  * wkd: New commands --print-wkd-hash and --print-wkd-url for
    gpg-wks-client.

  Release-info: https://dev.gnupg.org/T4434

Update gnupg to 2.2.14, pet portlint, and remove a redundant readline
dependency.

  * gpg: Allow import of PGP desktop exported secret keys.  Also avoid
   importing secret keys if the secret keyblock is not valid.  [#4392]

  * gpg: Do not error out on version 5 keys in the local keyring.

  * gpg: Make invalid primary key algo obvious in key listings.

  * sm: Do not mark a certificate in a key listing as de-vs compliant
    if its use for a signature will not be possible.

  * sm: Fix certificate creation with key on card.

Update gnupg to 2.2.13

  * gpg: Implement key lookup via keygrip (using the & prefix).

  * gpg: Allow generating Ed25519 key from existing key.

  * gpg: Emit an ERROR status line if no key was found with -k.

  * gpg: Stop early when trying to create a primary Elgamal key.  [#4329]

  * gpgsm: Print the card's key algorithms along with their keygrips
    in interactive key generation.

  * agent: Clear bogus pinentry cache in the error case.  [#4348]

  * scd: Support "acknowledge button" feature.

  * scd: Fix for USB INTERRUPT transfer.  [#4308]

  * wks: Do no use compression for the the encrypted challenge and
    response.

  Release-info: https://dev.gnupg.org/T4290

Update gnupg to 2.2.12

 * tools: New commands --install-key and --remove-key for
    gpg-wks-client.  This allows to prepare a Web Key Directory on a
    local file system for later upload to a web server.

  * gpg: New --list-option "show-only-fpr-mbox".  This makes the use
    of the new gpg-wks-client --install-key command easier on Windows.

  * gpg: Improve processing speed when --skip-verify is used.

  * gpg: Fix a bug where a LF was accidentally written to the console.

  * gpg: --card-status now shwos whether a card has the new KDF
    feature enabled.

Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.

PR:		231590

Install texinfo files (GNU info) into ${PREFIX}/share/info

After a discussion on the mailing list on moving manpages to
${PREFIX}/share/man for consistency with base where it is
installed in usr/share/man, it appeared the same should happen
to GNU info files which were installed under share in base and
not in ports.

Now texinfo is not in base on any of the supported version of FreeBSD
it is possible to proceed to this move and it is easier to do than
the manpage change.

Other benefit than consistency are less patching: all build tools but
cmake are expecting info files to be under share/info and cmake (patched here)
was having an exception for BSD so the patch makes FreeBSD case less
specific for them

Bump revision of all impacted ports

PR:		232907
exp-run by:	antoine
Differential Revision:	https://reviews.freebsd.org/D17816

Update gnupg to 2.2.11

  * gpgsm: Fix CRL loading when intermediate certicates are not yet
    trusted.

  * gpgsm: Fix an error message about the digest algo.  [#4219]

  * gpg: Fix a wrong warning due to new sign usage check introduced
    with 2.2.9.  [#4014]

  * gpg: Print the "data source" even for an unsuccessful keyserver
    query.

  * gpg: Do not store the TOFU trust model in the trustdb.  This
    allows to enable or disable a TOFO model without triggering a

security/gnupg: Add pkg-message about potential connectivity issues

GnuPG, when run on hosts without IPv6 connectivity, may fail to connect to
dual-stack hkp servers [1].  Describe a workaround in pkg-message.

[1] https://dev.gnupg.org/rGecfc4db3a2f8bc2652ba4ac4de5ca1cd13bfcbec

Approved by:	adamw (maintainer)
Differential Revision:	https://reviews.freebsd.org/D17071

gnupg: Fix spelling of SUID_GPG

Update gnupg to 2.2.10 and add LARGE_RSA option

The LARGE_RSA option [1] enables 8192-bit keys, though GnuPG's lead
author does not recommend using it routinely.

Also, sort OPTIONS, and move an explanation of the SUID option from
the Makefile into pkg-help, where it belongs.

Major changes:
  gpg: Refresh expired keys originating from the WKD.
  gpg: Use a 256 KiB limit for a WKD imported key.
  gpg: New option --known-notation.
  scd: Add support for the Trustica Cryptoucan reader.
  agent: Speed up starting during on-demand launching.
  dirmngr: Validate SRV records in WKD queries.
  Release-info: https://dev.gnupg.org/T4112

PR:		230610 [1]
Submitted by:	Dmitri Goutnik
Reported by:	p5B2E9A8F t online de

Bump PORTREVISION for ports depending on the canonical version of GCC
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.

This includes ports
 - featuring USE_GCC=yes or USE_GCC=any,
 - featuring USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and those
 - with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
   c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.

PR:		222542

Update gnupg to 2.2.9

  * dirmngr: Fix recursive resolver mode and other bugs in the libdns
    code.  [#3374,#3803,#3610]

  * dirmngr: When using libgpg-error 1.32 or later a GnuPG build with
    NTBTLS support (e.g. the standard Windows installer) does not
    anymore block for dozens of seconds before returning data.  If you
    still have problems on Windows, please consider to use one of the
    options disable-ipv4 or disable-ipv6.

  * gpg: Fix bug in --show-keys which actually imported revocation
    certificates.  [#4017]

  * gpg: Ignore too long user-ID and comment packets.  [#4022]

Update gnupg to 2.2.8 (security release)

CVE-2018-12020:
The OpenPGP protocol allows to include the file name of the original
input file into a signed or encrypted message.  During decryption and
verification the GPG tool can display a notice with that file name.  The
displayed file name is not sanitized and as such may include line feeds
or other control characters.  This can be used inject terminal control
sequences into the out and, worse, to fake the so-called status
messages.  These status messages are parsed by programs to get
information from gpg about the validity of a signature and an other
parameters.  Status messages are created with the option "--status-fd N"
where N is a file descriptor.  Now if N is 2 the status messages and the
regular diagnostic messages share the stderr output channel.  By using a
made up file name in the message it is possible to fake status messages.

Update gnupg to 2.2.7

Also, remove unnecessary USE_LDCONFIG.

  * gpg: New option --no-symkey-cache to disable the passphrase cache
    for symmetrical en- and decryption.

  * gpg: The ERRSIG status now prints the fingerprint if that is part
    of the signature.

  * gpg: Relax emitting of FAILURE status lines

  * gpg: Add a status flag to "sig" lines printed with --list-sigs.

  * gpg: Fix "Too many open files" when using --multifile.  [#3951]

Update gnupg to 2.2.6

  * gpg,gpgsm: New option --request-origin to pretend requests coming
    from a browser or a remote site.

  * gpg: Fix race condition on trustdb.gpg updates due to too early
    released lock.  [#3839]

  * gpg: Emit FAILURE status lines in almost all cases.  [#3872]

  * gpg: Implement --dry-run for --passwd to make checking a key's
    passphrase straightforward.

  * gpg: Make sure to only accept a certification capable key for key
    signatures.  [#3844]

Update gnupg to 2.2.5

Changes: https://lists.gnupg.org/pipermail/gnupg-announce/2018q1/000420.html

Update gnupg to 2.2.4. Bump the libassuan requirement to 2.5.1.

  * gpg: Change default preferences to prefer SHA512.

  * gpg: Print a warning when more than 150 MiB are encrypted using a
    cipher with 64 bit block size.

  * gpg: Print a warning if the MDC feature has not been used for a
    message.

  * gpg: Fix regular expression of domain addresses in trust
    signatures. [#2923]

  * agent: New option --auto-expand-secmem to help with high numbers
    of concurrent connections.  Requires libgcrypt 1.8.2 for having

Update to 2.2.3

 * gpgsm: Fix initial keybox creation on Windows. [#3507]

 * dirmngr: Fix crash in case of a CRL loading error. [#3510]

 * Fix the name of the Windows registry key. [Git#4f5afaf1fd]

 * gpgtar: Fix wrong behaviour of --set-filename. [#3500]

 * gpg: Silence AKL retrieval messages. [#3504]

 * agent: Use clock or clock_gettime for calibration. [#3056]

 * agent: Improve robustness of the shutdown pending
   state. [Git#7ffedfab89]

Update to 2.2.2

Also, improve COMMENT, which conflicted with the pkg-descr.

 * gpg: Avoid duplicate key imports by concurrently running gpg
   processes. [#3446]

 * gpg: Fix creating on-disk subkey with on-card primary key. [#3280]

 * gpg: Fix validity retrieval for multiple keyrings. [Debian#878812]

 * gpg: Fix --dry-run and import option show-only for secret keys.

 * gpg: Print "sec" or "sbb" for secret keys with import option
   import-show. [#3431]

Update gnupg to 2.2.1, and remove the security/gnupg22 port

I misjudged the timeline for 2.3, and had not processed that the
intent of 2.3 is different from 2.1. Rather than 2.3 being a "modern"
branch and 2.2 being purely "stable," 2.3 will be development and
users are encouraged to remain on 2.2. Furthermore, upstream doesn't
expent a 2.3 release for a year or so.

Accordingly, I'm removing the gnupg22 port and updating security/gnupg
to be 2.2. gnugp20 is still scheduled for deletion at the end of the
year.

Bump PORTREVISION for ports depending on the canonical version of GCC
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang,
   c++14-lang, c++0x, c11, or gcc-c++11-lib.

PR:		219275

Add gnupg22 port. GnuPG 2.2 is the new LTS stable version. gnupg20 is
now marked for deprecation at the end of the year (when upstream support
for it will end). Users of gnupg20 should migrate to gnupg22.

The gnupg port is remaining at 2.1.x for now, as it's essentially the
same thing as 2.2.0. It will become 2.3 soon-ish.

Update to 2.1.23, and use the correct TEST_TARGET.


 * gpg: Options --auto-key-retrieve and --auto-key-locate "local,wkd"
   are now used by default.  Note: this enables keyserver and Web Key
   Directory operators to notice when a signature from a locally
   non-available key is being verified for the first time or when
   you intend to encrypt to a mail address without having the key
   locally.  This new behaviour will eventually make key discovery
   much easier and mostly automatic.  Disable this by adding
     no-auto-key-retrieve
     auto-key-locate local
   to your gpg.conf.

 * agent: Option --no-grab is now the default.  The new option --grab

Update to 2.1.22.

Noteworthy changes in version 2.1.22
====================================

 * gpg: Extend command --quick-set-expire to allow for setting the
   expiration time of subkeys.

 * gpg: By default try to repair keys during import.  New sub-option
   no-repair-keys for --import-options.

 * gpg,gpgsm: Improved checking and reporting of DE-VS compliance.

 * gpg: New options --key-origin and --with-key-origin.  Store the
   time of the last key update from keyservers, WKD, or DANE.

Update devel/readline to 7.0 patch 3

- Bump PORTREVISION for shlib change

Changes:	https://cnswww.cns.cwru.edu/php/chet/readline/CHANGES
		https://lists.gnu.org/archive/html/bug-bash/2016-09/msg00107.html
		https://lists.gnu.org/archive/html/bug-readline/2017-01/msg00002.html
Differential Revision:	https://reviews.freebsd.org/D11172
PR:		219947
Exp-run by:	antoine

Ignore errors about missing smartcard daemon.

It's an OPTION on FreeBSD, but 2.1.21 treated missing scdaemon as an
error.

PR:		219400
Submitted by:	Philip Jocks
Obtained from:	https://dev.gnupg.org/rGa8dd96826f8484c0ae93c954035b95c2a75c80f2
See also:	https://lists.gnupg.org/pipermail/gnupg-users/2017-May/058233.html
MFH:		2017Q2

Update to 2.1.21, which in particular fixes a keyring corruption bug.


  * gpg,gpgsm: Fix corruption of old style keyring.gpg files.  This
    bug was introduced with version 2.1.20.  Note that the default
    pubring.kbx format was not affected.

  * gpg,dirmngr: Removed the skeleton config file support.  The
    system's standard methods for providing default configuration
    files should be used instead.

  * w32: The Windows installer now allows installion of GnuPG without
    Administrator permissions.

  * gpg: Fixed import filter property match bug.

  * scd: Removed Linux support for Cardman 4040 PCMCIA reader.

  * scd: Fixed some corner case bugs in resume/suspend handling.

  * Many minor bug fixes and code cleanup.

MFH:		2017Q2

Update to 2.1.20.

 * gpg: New properties 'expired', 'revoked', and 'disabled' for the
   import and export filters.

 * gpg: New command --quick-set-primary-uid.

 * gpg: New compliance field for the --with-colon key listing.

 * gpg: Changed the key parser to generalize the processing of local
   meta data packets.

 * gpg: Fixed assertion failure in the TOFU trust model.

 * gpg: Fixed exporting of zero length user ID packets.

Bump PORTREVISIONs for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using using Mk/bsd.octave.mk which in turn has USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
   c++11-lang, c++0x, c11, or gcc-c++11-lib.

PR:		216707

Update to 2.1.19.

Noteworthy changes in version 2.1.19
====================================

  * gpg: Print a warning if Tor mode is requested but the Tor daemon
    is not running.

  * gpg: New status code DECRYPTION_KEY to print the actual private
    key used for decryption.

  * gpgv: New options --log-file and --debug.

  * gpg-agent: Revamp the prompts to ask for card PINs.

Update to 2.1.18

Noteworthy changes in version 2.1.18
====================================

 * gpg: Remove bogus subkey signature while cleaning a key (with
   export-clean, import-clean, or --edit-key's sub-command clean)

 * gpg: Allow freezing the clock with --faked-system-time.

 * gpg: New --export-option flag "backup", new --import-option flag
   "restore".

 * gpg-agent: Fixed long delay due to a regression in the progress
   callback code.

Enable the SCDAEMON option by default.

Requested by:	Dave Horn

Update GnuPG to 2.1.17 which resolves the following error that resulted when
attempting to use the --export-ssh-key option.

gpg: Ohhhh jeeee: Assertion "ret_found_key == NULL || ret_keyblock != NULL" in
lookup failed (getkey.c:3677)

The KDNS option is removed with this update because upstream dropped use of
adns in favor of a bundled libdns which is used by default. Also, removed an
obsolete patch.

PR:		216057
Submitted by:	Matthew Rezny

Use the -f flag when creating the gpg -> gpg2 link because test -e returns
false for dead links and ln should be allowed to replace them.
Simplify removal of the link on uninstall.

Approved by:	adamw (maintainer)

A little more detail into COMMENT, reflow the pkg-descr, and use pro mode
for the plist.

Simplify, reformat, and modernize.

The user-facing changes, some of which required a PORTREVISION bump:

* Don't make everybody download the signature file
* Add USES=readline, rather than making assumptions about it being in
  /usr. A side effect of this was that gnupg was being built with
  readline support on 10 but not 11, except when LDAP was enabled which
  brought it in as a side effect
* Don't make manpages dependent upon the DOCS option. As a side effect,
  everybody now gets the info files. Also, put the help files into
  DOCSDIR instead of DATADIR; best as I can tell they aren't being
  called from within gpg
* Reword the pkg-descr to describe what gpg is, rather than making a
  frightening-sounding statement about patents and unrestricted use
* Handle the gpg symlink in the plist, and be a little looser about
  creating it and tighter about removing it
* Remove the pkg-message. The pinentry dependency installs a pinentry
  dialogue already

Take maintainership of the rest of the gnupg* ports from kuriyama, who
is slimming his portfolio. He created the gnupg ports over 18 years ago
and he has looked after them this whole time. Deepest thanks to him
for the incredible amount of work and time that's gone into these ports!

security/gnupg: fix build on 9.x

gnupg fails to build on 9.x with:

  mime-parser.h:53: error: redefinition of typedef 'rfc822parse_t'
  rfc822parse.h:23: error: previous declaration of 'rfc822parse_t' was here

Add compiler:c11 to USES to fix that.

Reported by:	antoine

security/gnupg: update to 2.1.16

This release fixes an issue that the previous gnupg release (2.1.15)
was incompatible with libgpg-error 1.25 that caused gpg-agent failing
to start.

PR:		214568
Submitted by:	cmt
Tested by:	cmt
Reported by:	many

update gnupg to 2.1.15

PR:		212355
Approved by:	rene (mentor)
Approved by:	maintainer timeout

- Upgrade to 2.1.13 (minor bugfixes).

- Upgrade to 2.1.12 (bugfixes).

Remove ${PORTSDIR}/ from dependencies, categories r, s, t, and u.

With hat:	portmgr
Sponsored by:	Absolight

- Update security/gnutls to 3.4.10.
- Rename the LIBDANE option DANE because that's the name of the protocol
  supported by libgnutls-dane and gnutls-cli.  Also clarify the option
  description.
- Add an IDN option.
- libgnutls-openssl has been removed in 3.4.  Some ports used this library
  in their LIB_DEPENDS but no port actually required it.
- Some old API functions have been removed.  Ports that used these have been
  updated or patched to use the new API.
- Add a patch to print/cups to prevent overlinking of libgnutls.so.
- Bump PORTREVISION on dependent ports.

net-im/jabber: This port used the old API to give users fine grained
control over which crypto algorithms were used via a configuration file.
It's not immediately obvious how to port this to the new API so the port
always uses the defaults now.

www/hydra: Mark BROKEN.  This uses more removed calls than the other ports,
is said to be alpha quality and not fully functional and has been abandoned
10 years ago.

PR:		207768
Exp-run by:	antoine
Approved by:	portmgr (antoine)

security/gnupg: ldap module needs gcrypt too

security/gnupg: fix build when NLS is disabled

Regenerate distinfo information for gnupg-2.1.11.tar.bz2.sig.

This fixes `make fetch'.

The actual hash and sizes are different, as mentioned in the associated PR.
I have also checked it manually, and verified the tarball's signature with
`gpg --verify gnupg-2.1.11.tar.bz2.sig gnupg-2.1.11.tar.bz2'.

I don't understand how this happened, but it looks similar to bug 202312.

PR:		207327
Submitted by:	Trond.Endrestol@ximalas.info

Update to 2.1.11 (minor fixes, with upstream patch).

- Upgrade to 2.1.8 (minor bugfixes).

Add more signature (locally verified).

PR:		ports/202312
Submitted by:	igorz@yandex.ru