SHA256
1
0
forked from pool/rnp
rnp/rnp.changes

77 lines
3.3 KiB
Plaintext

-------------------------------------------------------------------
Mon Sep 26 04:36:06 UTC 2022 - Andreas Stieger <andreas.stieger@gmx.de>
- rnp 0.16.2:
* Support a number of additional key and encryption operations
* Now uses separate security rules for the data and key signatures,
extending SHA1 key signature support till the Jan, 19 2024.
* The default key expiration time was set to 2 years.
* The library got a number of developer visible updates,
and the command-line interface gained a number of additional
knobs, switches, and output improvements
-------------------------------------------------------------------
Sun May 22 08:14:29 UTC 2022 - Andreas Stieger <andreas.stieger@gmx.de>
- add upstream signing key and verify source signature
-------------------------------------------------------------------
Sun Feb 13 18:12:53 UTC 2022 - Andreas Stieger <andreas.stieger@gmx.de>
- rnp 0.16.0:
* Ability to disable certain features via compile-time switches
(ENABLE_AEAD, ENABLE_SM2, etc.)
* Mark signatures with SHA1/MD5 hash, produced after the specific
date (2019-01-19 and 2012-01-01) as invalid
* Fixed possible incompatibility with GnuPG on x25519 secret key
export
* Fixed export of non-FFI symbols from rnp.so/rnp.dylib
* Fixed key expiration time calculation in some edge cases
* Added security profile manipulation functions to the FFI
* Improved CLI tools help messages
* Improved CLI: stdin/stdout/env input/output specifiers, --notty
for batch processing, etc.
-------------------------------------------------------------------
Sat Jan 15 08:14:17 UTC 2022 - Andreas Stieger <andreas.stieger@gmx.de>
- disable tests
-------------------------------------------------------------------
Mon Aug 9 20:44:23 UTC 2021 - Andreas Stieger <andreas.stieger@gmx.de>
- rnp 0.15.2:
* Be less strict in userid validation: allow to use userids with
self-signature, which has key expiration in the past
* Do not mark signature as invalid if key which produced it is
expired now, but was valid during signing
* Fix incorrect key expiration calculation in some cases
* rnp: Show error message if encryption failed
* rnpkeys: Add --expiration option to specify expiration time
during key generation
- run tests
-------------------------------------------------------------------
Mon Jun 28 20:17:02 UTC 2021 - Andreas Stieger <andreas.stieger@gmx.de>
- rnp 0.15.1:
* Fix updating of expiration time for a key with multiple user
IDs
* Fixed key expiry check for keys valid after the year 2038
* Pick up key expiration time from direct-key signature or primary
userid certification if available
* CVE-2021-33589: issue with cleartext key data after the
rnp_key_unprotect()/rnp_key_protect() calls (boo#1187759)
- includes changes from 0.15.0:
* Improve handling of cleartext signatures, when empty line
between headers and contents contains some whitespace
* Relax requirements for the armored messages CRC (allow absence
of the CRC, and issue warning instead of complete failure)
* documentation updates
* rnpkeys: add --remove-key command
-------------------------------------------------------------------
Sun Feb 21 21:44:24 UTC 2021 - Andreas Stieger <andreas.stieger@gmx.de>
- initial package, 0.14.0