{"id":99690,"date":"2021-04-08T22:22:55","date_gmt":"2021-04-08T20:22:55","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-gnupg-2-3-0"},"modified":"2021-04-08T22:22:55","modified_gmt":"2021-04-08T20:22:55","slug":"vypusk-gnupg-2-3-0","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-gnupg-2-3-0","title":{"rendered":"Release of GnuPG 2.3.0","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
After three and a half years since the formation of the last significant branch, a new release of the GnuPG toolkit 2.3.0 (GNU Privacy Guard) has been introduced, compatible with OpenPGP (RFC-4880) and S\/MIME standards, providing utilities for data encryption, working with digital signatures, key management, and access to public key repositories. <\/p>\n
GnuPG 2.3.0 is positioned as the first release of a new codebase that includes the latest developments. GnuPG 2.2 is regarded as the stable branch, optimal for widespread use, which will be supported for at least until 2024. GnuPG 1.4 continues to be maintained as a classic series that consumes minimal resources, suitable for embedded systems, and compatible with outdated encryption algorithms. <\/p>\n
Key innovations in GnuPG 2.3.0: <\/p>\n
\n
An experimental background process has been proposed with a key database implementation using SQLite for storage, demonstrating faster key searches. To enable the new storage, the option 'use-keyboxd' should be activated in gpg.conf and gpgsm.conf.\n
A new utility gpg-card has been added, which can be used as a flexible interface for all supported types of smart cards.\n
A new background process tpm2d has been added, allowing the use of TPM 2.0 chips to protect private keys and perform encryption operations or create digital signatures on the TPM module side.\n
The default algorithms for public keys are now ed25519 and cv25519.\n
In gpg, the use of encryption algorithms with a block size of 64 bits has been discontinued. The use of 3DES is prohibited, and AES is declared as the minimally supported algorithm. To disable this restriction, the option '--allow-old-cipher-algos' can be used.\n
Support for AEAD modes of block encryption OCB and EAX has been added.\n
Support for version 5 of keys and digital signatures has been provided.\n
Support for X448 curves (ed448, cv448) has been added.\n
The use of group names in key lists is now allowed.\n
In gpg, verification results now depend on the '--sender' option and the signature creator's identifier.\n
In gpg, gpgsm, gpgconf, gpg-card, and gpg-connect-agent, the '--chuid' option has been added for changing the user identifier.\n
In gpg, the options '--full-timestrings' (for date and time output), '--force-sign-key', and '--no-auto-trust-new-key' have been added.\n
Support for the deprecated PKA key discovery method has been discontinued, and associated options have been removed.\n
The ability to export Ed448 keys for SSH has been added in gpg.\n
Basic ECC support and the ability to create EdDSA certificates have been added in gpgsm.\n
In the agent, the value 'Label:' is now allowed in the key file to configure the PIN input prompt. Support for ssh-agent extensions for environment variables has been implemented.\n
In scd, support for multiple card readers and tokens has been improved. The ability to use multiple applications with a specific smart card has been implemented. Support for PIV cards, Telesec Signature Cards v2.0, and Rohde&Schwarz Cybersecurity has been added. New options '--application-priority' and '--pcsc-shared' have been introduced.\n
The symcryptrun utility has been removed (an outdated wrapper over the external utility Chiasmus).\n
Full Unicode support in the command line has been implemented on the Windows platform. <\/ul>\n