I have been on holidays, so I noticed this message only last week. I will
try the new version to check whether the problem with ZSK rollovers is
solved, when using more than one ZSK. This will take some time.
I already noticed that the output of "ods-enforcer backup list" has not yet
been changed into something readable. Is that still in the planning?
"Yuri Schaeffer" schreef in bericht
news:365a8432-514f-62eb--e4df8b1d3...@nlnetlabs.nl...
Dear community,
Hereby we announce the OpenDNSSEC 2.0.3 release. Most of the changes are
related to further smoothing the migration path from OpenDNSSEC 1.4 to
2.0. If you still need to migrate from 1.4.10 please migrate to 2.0.3
directly rather than from 2.0.1. Another important fix is a memory leak
in the signer. It would cause a high memory usage for installations with
very frequent outgoing IXFR's.
Changes:
* OpenDNSSEC-839: update all no longer deletes zones or policies.
Policy import now has a --remove-missing-policies option. (thanks
David Peall)
* OpenDNSSEC-840: Fix migration script to correctly interpret SOA
serial strategy.
* OPENDNSSEC-843: MaxZoneTTL defaults to 0 instead of 1 day.
* Migration script can handle converting a database with zones in
rollover better.
* Fixed incorrect behaviour when more than 2 ZSKs involved in roll.
* SUPPORT-201: Remove old keys from converted DB.
* OPENDNSSEC-845: Memory leak on IXFR out.
Download:
* https://dist.opendnssec.org/source/opendnssec-2.0.3.tar.gz
* https://dist.opendnssec.org/source/opendnssec-2.0.3.tar.gz.sig
* Checksum SHA256:
ebeb5481d696cf83c21c5dfbecce6ab5dcc73df1a08573ef257f2f6fe10f6214
Kind regards,
The OpenDNSSEC team
___
Opendnssec-user mailing list
Opendnssec-user@lists.opendnssec.org
https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
