summaryrefslogtreecommitdiff
path: root/security/gnupg
AgeCommit message (Collapse)AuthorFilesLines
2005-05-22Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions:jlam1-2/+2
USE_GNU_TOOLS -> USE_TOOLS awk -> gawk m4 -> gm4 make -> gmake sed -> gsed yacc -> bison
2005-05-15gzcat is needed, so note it as such for the new tools framework.jlam1-1/+2
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-03-22Update to 1.4.1:wiz4-36/+26
Noteworthy changes in version 1.4.1 (2005-03-15) ------------------------------------------------ * New --rfc2440-text option which controls how text is handled in signatures. This is in response to some problems seen with certain PGP/MIME mail clients and GnuPG version 1.4.0. More details about this are available at <http://lists.gnupg.org/pipermail/gnupg-users/2005-January/024408.html>. * New "import-unusable-sigs" and "export-unusable-sigs" tags for --import-options and --export-options. These are off by default, and cause GnuPG to not import or export key signatures that are not usable (e.g. expired signatures). * New experimental HTTP, HTTPS, FTP, and FTPS keyserver helper that uses the cURL library <http://curl.haxx.se> to retrieve keys. This is disabled by default, but may be enabled with the configure option --with-libcurl. Without this option, the existing HTTP code is used for HTTP, and HTTPS, FTP, and FTPS are not supported. [enabled with the "curl" option for the package] * When running a --card-status or --card-edit and a public key is available, missing secret key stubs will be created on the fly. Details of the key are listed too. * The implicit packet dumping in double verbose mode is now sent to stderr and not to stdout. * Added countermeasures against the Mister/Zuccherato CFB attack <http://eprint.iacr.org/2005/033>. * Add new --edit-key command "bkuptocard" to allow restoring a card key from a backup. * The "fetch" command of --card-edit now retrieves the key using the default keyserver if no URL has been stored on the card. * New configure option --enable-noexecstack. Also, gpgkeys_mailto is not installed any longer, dropping the dependency on perl.
2005-02-24Add RMD160 digests.agc1-1/+2
2005-02-09Disable gnupg's new iconv code on platforms that have problems with itmarkd1-1/+5
in the default locale (NetBSD < 2.0 and Solaris). OK'ed by wiz. Fixes PR pkg/28895.
2004-12-25Add options.mk file.wiz1-0/+56
2004-12-25Update to 1.4.0, provided by Stefan Krüger in PR 28738.wiz10-140/+33
While here, convert to options.mk. GnuPG 1.4 Highlights ==================== This is a brief overview of the changes between the GnuPG 1.2 series and the new GnuPG 1.4 series. To read the full list of highlights for each revision that led up to 1.4, see the NEWS file in the GnuPG distribution. This document is based on the NEWS file, and is thus the highlights of the highlights. When upgrading, note that RFC-2440, the OpenPGP standard, is currently being revised. Most of the revisions in the latest draft (2440bis-12) have already been incorporated into GnuPG 1.4. Algorithm Changes ----------------- OpenPGP supports many different algorithms for encryption, hashing, and compression, and taking into account the OpenPGP revisions, GnuPG 1.4 supports a slightly different algorithm set than 1.2 did. The SHA256, SHA384, and SHA512 hashes are now supported for read and write. The BZIP2 compression algorithm is now supported for read and write. Due to the recent successful attack on the MD5 hash algorithm (discussed in <http://www.rsasecurity.com/rsalabs/node.asp?id=2738>, among other places), MD5 is deprecated for OpenPGP use. It is still allowed in GnuPG 1.4 for backwards compatibility, but a warning is given when it is used. The TIGER/192 hash is no longer available. This should not be interpreted as a statement as to the quality of TIGER/192 - rather, the revised OpenPGP standard removes support for several unused or mostly unused hashes, and TIGER/192 was one of them. Similarly, Elgamal signatures and the Elgamal signing key type have been removed from the OpenPGP standard, and thus from GnuPG. Please do not confuse Elgamal signatures with DSA or DSS signatures or with Elgamal encryption. Elgamal signatures were very rarely used and were not supported in any product other than GnuPG. Elgamal encryption was and still is part of OpenPGP and GnuPG. Very old (pre-1.0) versions of GnuPG supported a nonstandard (contrary to OpenPGP) Elgamal key type. While no recent version of GnuPG permitted the generation of such keys, GnuPG 1.2 could still use them. GnuPG 1.4 no longer allows the use of these keys or the (also nonstandard) messages generated using them. At build time, it is possible to select which algorithms will be built into GnuPG. This can be used to build a smaller program binary for embedded uses where space is tight. Keyserver Changes ----------------- GnuPG 1.4 does all keyserver operations via plugin or helper applications. This allows the main GnuPG program to be smaller and simpler. People who package GnuPG for various reasons have the flexibility to include or leave out support for any keyserver type as desired. Support for fetching keys via HTTP and finger has been added. This is mainly useful for setting a preferred keyserver URL like "http://www.jabberwocky.com/key.asc". or "finger:wk at g10code.com". The LDAP keyserver helper now supports storing, retrieving, and searching for keys in both the old NAI "LDAP keyserver" as well as the more recent method to store OpenPGP keys in standard LDAP servers. This is compatible with the storage schema that PGP uses, so both products can interoperate with the same LDAP server. The LDAP keyserver helper is compatible with the PGP company's new "Global Directory" service. If the LDAP library you use supports LDAP-over-TLS and LDAPS, then GnuPG detects this and supports them as well. Note that using TLS or LDAPS does not improve the security of GnuPG itself, but may be useful in certain key distribution scenarios. HTTP Basic authentication is now supported for all HKP and HTTP keyserver functions, either through a proxy or via direct access. The HKP keyserver plugin supports the new machine-readable key listing format for those keyservers that provide it. IPv6 is supported for HKP and HTTP keyserver access. When using a HKP keyserver with multiple DNS records (such as subkeys.pgp.net which has the addresses of multiple servers around the world), all DNS address records are tried until one succeeds. This prevents a single down server in the rotation from stopping access. DNS SRV records are used in HKP keyserver lookups to allow administrators to load balance and select keyserver ports automatically. Timeout support has been added to the keyserver plugins. This allows users to set an upper limit on how long to wait for the keyserver before giving up. Preferred Keyserver URL ----------------------- Preferred keyserver support has been added. Users may set a preferred keyserver via the --edit-key command "keyserver". If the --keyserver-option honor-keyserver-url is set (and it is by default), then the preferred keyserver is used when refreshing that key with --refresh-keys. The --sig-keyserver-url option can be used to inform signature recipients where the signing key can be downloaded. When verifying the signature, if the signing key is not present, and the keyserver options honor-keyserver-url and auto-key-retrieve are set, this URL will be used to retrieve the key. Trust Signatures ---------------- GnuPG 1.4 supports OpenPGP trust signatures, which allow a user to specify the trust level and distance from the user along with the signature so users can delegate different levels of certification ability to other users, possibly restricted by a regular expression on the user ID. Trust Models ------------ GnuPG 1.4 supports several ways of looking at trust: Classic - The classic PGP trust model, where people sign each others keys and thus build up an assurance (called "validity") that the key belongs to the right person. This was the default trust model in GnuPG 1.2. Always - Bypass all trust checks, and make all keys fully valid. Direct - Users may set key validity directly. PGP - The PGP 7 and 8 behavior which combines Classic trust with trust signatures overlaid on top. This is the default trust model in GnuPG 1.4. The OpenPGP Smartcard --------------------- GnuPG 1.4 supports the OpenPGP smartcard (<http://www.g10code.de/p-card.html>) Secret keys may be kept fully or partially on the smartcard. The smartcard may be used for primary keys or subkeys. Other Interesting New Features ------------------------------ For those using Security-Enhanced Linux <http://www.nsa.gov/selinux/>, the configure option --enable-selinux-support prevents GnuPG from processing its own files (i.e. reading the secret keyring for something other than getting a secret key from it). This simplifies writing ACLs for the SELinux kernel. Readline support is now available at all prompts if the system provides a readline library. GnuPG can now create messages that can be decrypted with either a passphrase or a secret key. These messages may be generated with --symmetric --encrypt or --symmetric --sign --encrypt. --list-options and --verify-options allow the user to customize exactly what key listings or signature verifications look like, enabling or disabling things such as photo display, preferred keyserver URL, calculated validity for each user ID, etc. The --primary-keyring option designates the keyring that the user wants new keys imported into. The --hidden-recipient (or -R) command encrypts to a user, but hides the identity of that user. This is the same functionality as --throw-keyid, but can be used on a per-user basis. Full algorithm names (e.g. "3DES", "SHA1", "ZIP") can now be used interchangeably with the short algorithm names (e.g. "S2", "H2", "Z1") anywhere algorithm names are used in GnuPG. The --keyid-format option selects short (99242560), long (DB698D7199242560), 0xshort (0x99242560), or 0xlong (0xDB698D7199242560) key ID displays. This lets users tune the display to what they prefer. While it is not recommended for extended periods, it is possible to run both GnuPG 1.2.x and GnuPG 1.4 during the transition. To aid in this, GnuPG 1.4 tries to load a config file suffixed with its version before it loads the default config file. For example, 1.4 will try for gpg.conf-1.4 and gpg.conf-1 before falling back to the regular gpg.conf file.
2004-11-08The correct name of this program is "GNU Privacy Guard" (not "Privacy Guard").tv1-2/+2
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv1-1/+2
in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include.
2004-08-26add back idea.c.gz (from USE_IDEA=yes). (hi wiz!)lukem1-1/+3
2004-08-26Update to 1.2.6:wiz3-21/+5
* Updated the included gettext. This also fixes the installation problem from 1.2.5 * Fixed a race condition possibly leading to deleted keys.
2004-08-05Regen to make GNU patch happy.minskim2-11/+5
2004-07-28Enable pkgviews installation.schmonz1-1/+5
2004-07-28Update to 1.2.5:wiz8-60/+38
* New --ask-cert-level/--no-ask-cert-level option to turn on and off the prompt for signature level when signing a key. Defaults to on. * New --min-cert-level option to disregard key signatures that are under a specified level. Defaults to 1 (i.e. don't disregard anything). * New --max-output option to limit the amount of plaintext output generated by GnuPG. This option can be used by programs which call GnuPG to process messages that may result in plaintext larger than the calling program is prepared to handle. This is sometimes called a "Decompression Bomb". * New --list-config command for frontends and other programs that call GnuPG. See doc/DETAILS for the specifics of this. * New --gpgconf-list command for internal use by the gpgconf utility from gnupg 1.9.x. * Some performance improvements with large keyrings. See --enable-key-cache=SIZE in the README file for details. * Some portability fixes for the OpenBSD/i386, HPPA, and AIX platforms. * Simplified Chinese translation.
2004-05-07whitespace nitscjep1-2/+2
2004-04-09Assume a mail transfer agent (/usr/sbin/sendmail) is installed.reed1-1/+2
This is to make sure that libexec/gnupg/gpgkeys_mailto is installed. (Okay'd by wiz.) This assumes that /usr/sbin/sendmail is sendmail. PKGREVISION is not bumped because package couldn't be made in first place if libexec/gnupg/gpgkeys_mailto was missing.
2004-04-08Convert to bl3.wiz1-8/+8
2004-03-30Apply the patch from PR pkg/21493. This is now submitted to gnupg.org astv4-6/+48
bug gnupg/293, so grant has blessed it for inclusion in pkgsrc. No more GNU sed build dependency, but the binaries do not change; thus PKGREVISION untouched.
2004-03-30compress USE_GNU_TOOLS onto one line.grant1-4/+2
2004-03-09Remove info files entries from PLIST.seb1-3/+1
2004-03-01Make build on m68kelf, and honour M68060 variable for quite a bitwiz3-3/+29
of speedup on m68060 machines. From S.P. Zeidler in PR 24579.
2004-02-08Install doc/DETAILS, which conveniently documents --with-colon formattedkleink2-2/+8
output, among other things. Bump to 1.2.4nb1. Approved by Thomas Klausner.
2004-02-02Respect whitespaces in SUBST_SED.fixme.xtraeme1-2/+2
2004-02-02Fix build in FreeBSD, the output was:xtraeme1-1/+13
_mpih-mul1.s:2: Error: alignment not a power of 2 _mpih-mul1.s:20: Error: alignment not a power of 2 So, changing ALIGN (3) to ALIGN (4) fixes these problems. Patch sent by pancake in private email, adapted to use subst.mk framework by me.
2004-01-24replace deprecated USE_GMAKE with USE_GNU_TOOLS+=make.grant1-2/+2
2003-12-25Update to 1.2.4:wiz9-110/+29
* Added read-only support for BZIP2 compression. This should be considered experimental, and is only available if the libbzip2 library <http://sources.redhat.com/bzip2/> is installed. * Added the ability to handle messages that can be decrypted with either a passphrase or a secret key. * Most support for Elgamal sign+encrypt keys has been removed. Old signatures may still be verified, and existing encrypted messages may still be decrypted, but no new signatures may be issued by, and no new messages will be encrypted to, these keys. Elgamal sign+encrypt keys are not part of the web of trust. The only new message that can be generated by an Elgamal sign+encrypt key is a key revocation. Note that in a future version of GnuPG (currently planned for 1.4), all support for Elgamal sign+encrypt keys will be removed, so take this opportunity to revoke old keys now. * A Russian translation is included again as well as a new Belarusian translation.
2003-12-01Add a patch to handle systems which have uint64_t but not the UINT64_Che2-1/+19
macro. This could happen with UNIX98-type systems, such as the code on our netbsd-1-5 branch, and would prevent this package from building on such systems. Problem also reported to the original author.
2003-11-27Add improved patch for compromised ElGamal signing keys fromheinz4-9/+83
gnupg-devel at gnupg org. The old patch didn't completely disable usage of the compromised keys. Move the old and new fix to the patches/ directory.
2003-11-27Apply security patch which disables ElGamal signature keys because theytron2-3/+9
are vulnerable. Bump package revision to reflect this change.
2003-10-11require GNU sed for GNU sed specific expressions.grant1-1/+3
fixes PR pkg/21493.
2003-08-25upgrade to 1.2.3.itojun6-44/+22
* New "--gnupg" option (set by default) that disables --openpgp, and the various --pgpX emulation options. This replaces --no-openpgp, and --no-pgpX, and also means that GnuPG has finally grown a --gnupg option to make GnuPG act like GnuPG. * A number of portability changes to make building GnuPG on less-common platforms easier. * Romanian translation. * Two new %-expandos for use in notation and policy URLs. "%g" expands to the fingerprint of the key making the signature (which might be a subkey), and "%p" expands to the fingerprint of the primary key that owns the key making the signature. * New "tru" record in --with-colons --list-keys listings. It shows the status of the trust database that was used to calculate the key validity in the listings. See doc/DETAILS for the specifics of this. * New REVKEYSIG status tag for --status-fd. It indicates a valid signature that was issued by a revoked key. See doc/DETAILS for the specifics of this.
2003-08-15add IPv6 support. bump PKGREVISIONitojun6-3/+89
2003-08-09USE_NEW_TEXINFO is unnecessary now.seb1-2/+1
2003-08-09Remove superfluous chunk which confuses some patch(1).wiz2-10/+3
2003-08-09fix for bad sh behaviour on Solaris (already available in latest GnuPG ↵heinz1-1/+2
snapshots)
2003-08-09fix for bad sh behaviour on Solaris (already available in latest GnuPG ↵heinz1-0/+23
snapshots)
2003-08-08Add http master site for idea.c.gz. Addresses PR 22408.wiz1-2/+3
2003-08-04Convert to USE_NEW_TEXINFO.seb2-7/+3
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-07-13PKGREVISION bump for libiconv update.wiz1-1/+2
2003-05-07fix checksum for USE_IDEA caseitojun1-3/+3
2003-05-06Remove dead mirrors, add a new one.tron1-4/+2
2003-05-06Fix some of the master site URLs so that the "fetch" target works attron1-5/+4
least particually.
2003-05-05Update gnupg package to 1.2.2.taca4-20/+10
Security problem is reported on bugtraq. http://www.securityfocus.com/archive/1/320444/2003-05-02/2003-05-08/0 2003-05-01 Werner Koch <wk@gnupg.org> Released 1.2.2. 2003-04-30 David Shaw <dshaw@jabberwocky.com> * NEWS: Note trust bug fix. 2003-04-29 David Shaw <dshaw@jabberwocky.com> * NEWS: Add note about TIGER being dropped from OpenPGP. * README: Add note about the HP/UX inline problem. Fix all URLs to point to the right place in the reorganized gnupg.org web pages. Some minor language fixes. 2003-04-27 David Shaw <dshaw@jabberwocky.com> * NEWS: Add sig version, pk algo, hash algo, and sig class to VALIDSIG. * BUGS: Fix bug reporting URL. 2003-04-24 Werner Koch <wk@gnupg.org> * configure.ac (ALL_LINGUAS): Added Hungarian translation by Nagy Ferenc László. 2003-04-23 David Shaw <dshaw@jabberwocky.com> * configure.ac: "TIGER" -> "TIGER/192". * README: Put back proper copyright line. 2003-04-16 Werner Koch <wk@gnupg.org> Released 1.2.2rc2. 2003-04-15 Werner Koch <wk@gnupg.org> * configure.ac (ALL_LINGUAS): Add Slovak translation. * configure.ac (HAVE_DOSISH_SYSTEM): New automake conditional. * acinclude.m4 (GNUPG_CHECK_ENDIAN): Fixed quoting of r.e. using quadrigraphs. 2003-04-08 David Shaw <dshaw@jabberwocky.com> * configure.ac: Big warning that TIGER is being removed from the standard. 2003-04-08 Werner Koch <wk@gnupg.org> * Makefile.am (EXTRA_DIST): Add autogen.sh wrapper which is useful for some cross-compiling targets. 2003-04-07 David Shaw <dshaw@jabberwocky.com> * acinclude.m4: Fix URL to faqprog.pl. * README: Add --enable-sha512 switch and update version number and copyright date. * NEWS: Add note about SHA-256/384/512. 2003-03-24 Werner Koch <wk@gnupg.org> * configure.ac: Test for ranlib and ar. 2003-03-12 Werner Koch <wk@gnupg.org> * acinclude.m4 (GNUPG_CHECK_ENDIAN): When crosscompiling assume little only for Intel CPUs. 2003-02-19 David Shaw <dshaw@jabberwocky.com> * configure.ac: Define @CAPLIBS@ to link in -lcap if we are using capabilities. 2003-02-11 David Shaw <dshaw@jabberwocky.com> * configure.ac: Add --enable-sha512 switch to add SHA384/512 support. 2003-02-06 David Shaw <dshaw@jabberwocky.com> * configure.ac: Do not set GNUPG_LIBEXECDIR in ./configure, so that makefiles can override it. 2003-02-02 David Shaw <dshaw@jabberwocky.com> * configure.ac (ALL_LINGUAS): Needs to be on one line to avoid problems during ./configure. * NEWS: Note new --with-colons disabled key flag and new "revuid" command. 2003-01-07 Werner Koch <wk@gnupg.org> Released 1.2.2rc1. * configure.ac (ALL_LINGUAS): Added fi and zh_TW. 2003-01-06 David Shaw <dshaw@jabberwocky.com> * NEWS: Add notes about disabled keys and trustdb tweaks. 2002-12-04 David Shaw <dshaw@jabberwocky.com> * NEWS: Add note about convert-from-106 script. 2002-11-25 David Shaw <dshaw@jabberwocky.com> * NEWS: Add notes about notation names and '@', the "--trust-model always" option, and non-optimized memory wiping. 2002-11-09 Werner Koch <wk@gnupg.org> * configure.ac: Check for ctermid(). 2002-10-31 David Shaw <dshaw@jabberwocky.com> * Makefile.am: Put gnupg.spec in the root directory so rpm -ta works. * configure.ac: Add a check for volatile.
2003-05-02Dependency bumps, needed because of devel/pth's major bump, and relatedwiz1-2/+2
dependency bumps.
2003-04-21Add RCS tagcjep1-0/+1
2003-04-01Don't try to use asm on any version of Darwin.thorpej2-1/+13
2003-01-10USE_PKGLOCALEDIR=yescjep1-7/+8
2003-01-09Update checksum for idea.c.gz.chris1-3/+3
Changelog from idea.c file indicates: * 2002-12-11 wk __ppc__ is used on Darwin instead of __powerpc__. Used .sig file to check download was ok. Closes pkg/19749
generated by cgit v1.2.3 (git 2.39.1) at 2025-02-22 23:10:24 +0000