GnuPG is a complete and free replacement for PGP. This is the "stable"
version.
GnuPG allows encrypting and signing your data and communication, and
features a versatile key management system as well as access modules
for many public key directories. GnuPG, also known as GPG, is a command
line tool with features for easy integration with other applications.
===> The following configuration options are available for gnupg25-2.5.20_1:
DOCS=on: Build and/or install documentation
GNUTLS=on: SSL/TLS support via GnuTLS
LARGE_RSA=off: Enable support for 8192-bit RSA keys
LDAP=off: LDAP keyserver interface
NLS=on: Native Language Support
SCDAEMON=on: Enable Smartcard daemon (with libusb)
SUID_GPG=off: Install GPG as SUID root
WKS_SERVER=on: Install the Web Key Service server
===> Use 'make config' to modify these settings
Affects: users of security/gnupg, security/gnupg25, security/gnupg1
Author: adridg@FreeBSD.org
Reason:
GnuPG 2.4 reaches end-of-life in July 2026. The 2.5 series is declared
stable upstream. Port security/gnupg25 will be retired and security/gnupg
is updated to the 2.5 series. As a result, users of security/gnupg25 must
switch (back) to security/gnupg. GnuPG 2.5 is backwards-compatible
with 2.4 and regular users of security/gnupg should experience no issues.
Upstream has removed co-installability with GnuPG 1.4, users that install
both security/gnupg and legacy security/gnupg1 will have to uninstall one.
Port Moves
port moved to security/gnupg on 2026-06-30 REASON: Has expired: Will roll up into security/gnupg
devel/gnupg25: new port 2.5.17, latest upstream
2.5.16 was (kind of suddenly, since I was waiting for 2.6) declared the
stable version. This was probably because of gpg.fail (which was partly
addressed by the previous update to 2.4.9).
Then 2.5.17 was released to address a number of critical security issues
introduced in the 2.5 branch. Release notes and discussion can
be found at
https://lwn.net/Articles/1056209/
Upstream release notes at
https://dev.gnupg.org/T7996
Marked as conflicting with gnupg1 and gnupg-2.4* because the names
of executables have changed again, and the "is-gpg2" flags went
away, so co-installability is poor.
