• Auditor: Include the zone name in the log messages.
• ldns 1.6.12 is required for bugfixes.
• ods-ksmutil: Suppress database connection information when no -v flag is given.
• ods-enforcerd: Stop multiple instances of the enforcer running by checking for the pidfile at startup. If you want to run multiple instances then a different pidfile will need to be specified with the -P flag.
• ods-ksmutil: “zone delete” renames the signconf file; so that if the zone is put back the signer will not pick up the old file.
• Signer Engine: Verbosity can now be set via conf.xml, default is 3.

Bugfixes:

• Bugfix OPENDNSSEC-174: Configure the location for conf.xml with –config or -c when starting the signer.
• Bugfix OPENDNSSEC-192: Signer crashed on deleting NSEC3 for a domain that becomes opt-out.
• Bugfix OPENDNSSEC-193: Auditor crashed with certain empty non-terminals.
• Signer Engine: A file descriptor for sockets with value zero is allowed.
• Signer Engine: Only log messages about a full signing queue in debug mode.
• Signer Engine: Fix time issues, make sure that the internal serial does not wander off after a failed audit.
• Signer Engine: Upgrade ldns to avoid future problems on 32-bit platforms with extra long signature expiration dates. More information in separate announcement.

Download the tarball from: opendnssec-1.3.5.tar.gz

• The library is now installed in $libdir/softhsm/

Bugfixes:

• Do not give a warning about the schema version if the token  has not been initialized yet.
• The tools now return the correct exit code.

Download the tarball from: softhsm-1.3.1.tar.gz

Affected versions: ldns < 1.6.12 (32-bit)
Fixed versions: ldns >= 1.6.12 (32-bit)

Description:
The 32-bit version of ldns has code for converting days since epoch to the day of year. That code had a bug which handled the end of the year in the wrong way. The result of the bug was that some signatures got the intended validity period extended by a year. The signature will be reused by the Signer Engine until the key is rolled. However, the Enforcer is not aware that there exist signatures with such a long validity period. Any affected signature will thus have no post-publication of its corresponding DNSKEY, possibly resulting in validation failure. There is also the risk that the affected signature will be used in a replay attack.

Test for affected signatures:
The affected signatures can be spotted by reviewing your signed zone. E.g. by using the following command:
> grep “20121231[0-9]\{6\} 2011″ signed.zone.file

Remove the affected signatures:
If there are signatures in the zone with extra long validity periods, then it is recommended to recreate all of the signatures. This is done by clearing the internal storage of the Signer Engine. You then wait for the next scheduled re-sign, but you can also force an immediate re-sign (the second command below) to speed up the process:
> ods-signer clear <zone>
> ods-signer sign <zone>

Mitigate replay attacks:
Once the affected signatures are removed from the zone, it may also be advisable to roll your keys. If you have a non-static zone and are changing your zone data, then there is a chance for an attacker to replay old data since the signature is still valid. You need to assess the risk and possible cost of such an attack. If you need to mitigate such an attack, then you need to roll your keys. Rolling keys will invalidate any signatures that an attacker may have stored for later use. If the signature of the DNSKEY RRset was affected, then you also need to roll the KSK:
> ods-ksmutil key rollover –zone <zone> –keytype ZSK
> ods-ksmutil key rollover –zone <zone> –keytype KSK

Solution:
The issue has been fixed in ldns 1.6.12. You should upgrade ldns before the end of this year.

Bugfixes:

• Signer: Use debug instead of warning for drudgers queue being full, also sleep 10 ms if it is full to not hog CPU. This increased signing speed on single core machines by a factor of 2.

Download the tarball from: opendnssec-1.3.4.tar.gz

Bugfixes:

• Auditor: Handle ruby 1.9 differences in ods-kaspcheck.
• Auditor: Require dnsruby 1.53 for bugfixes.
• Bugfix #262: Drudgers seem to be in a waiting state, but the RRset FIFO queue is full. Do an additional broadcast.
• Enforcer: Check HSM connection when waking up from sleep, attempt to reconnect if it is not valid. (r5511 in trunk, ported into the branch due to issues seen when CKR_DEVICE_ERROR returned by HSM.)
• libhsm: Added hsm_check_context() to check if the associated sessions are still alive. (Required for the above.)
• ods-ksmutil: key import was not setting the retire time.
• Signer Engine: Fix a threading issue, that could leave a zone without a task.
• Signer Engine: Update the signed zone file if only the $TTL or explicit TTL has been changed.
• Signer Engine: Remove the NSEC3PARAM RR when doing NSEC3 to NSEC rollover.
• Signer Engine: Deal with carriage returns (dos format) in zone file.
• Signer Engine: is PT0S means that refresh equals signtime.
• Signer Engine: Defense in depth in signer for duplicate keys.
• Signer Engine: Make sure that all required zonelist elements exist, otherwise error.
• Signer Engine: Warn the user if the serial is b0rk, and you can not use the serial from the signconf.
• Signer Engine: Log Auditor exit code.
• Fix a similar bug like #257: Error in ods-signerd, where a corrupted backup file results in an invalid pointer free().

Download the tarball from: opendnssec-1.3.3.tar.gz

Changes:

• Support for RollOverType in kasp.xml
• Fixed concurrency related crashes.
• Automatically retract never submitted DS records.
• Schedule the purging of keys.
• Automatic introduce keys marked as manual, like other enforcer.
• Do not allow lifetime of key to be shorter than TTL.
• CSK is now configurable.
• Remove some scheduling when waiting for user input.

Read more information about the Enforcer NG:
README.enforcer_testers

Download the snapshot from our SVN:
OpenDNSSEC-enforcer-ng-20111018

HIGH-LEVEL DESIGN GOALS

• Support for a large number of zones.
  The enforcer should reasonably be useable with many zones. Think order of magnitude 50.000 concurrent zones.
• Allow for future rollover strategies.
  Provide a generic framework to implement other kinds of rollovers in the future.
• Drop in replacement.
  Should replace the current enforcer but keep the same interface and provide migration scripts from earlier installs.

Read more information about the Enforcer NG:
README.enforcer_testers

Download the snapshot from our SVN:
OpenDNSSEC-enforcer-ng-20110922

Bugfixes:

• Bugfix #257: Error in ods-signerd, where a corrupted backup file results in an invalid pointer free().
• Signer Engine: Mark that a zone has a valid signer configuration, after recovering the zone from the backup files.

Download the tarball from: opendnssec-1.3.2.tar.gz

Bugfixes:

• Auditor: Fix ‘ZSK in use too long’ message to handle new signer behaviour.
• Bugfix #255: RHEL6 patch to contrib/opendnssec.spec. (Rick van Rein)
• Bugfix #256: Make sure argument in “ods-control signer” is not stripped off.
• Bugfix #259: ods-ksmutil: Prevent MySQL username or password being interpreted by the shell when running “ods-ksmutil setup”.
• Bugfix #260: “ods-ksmutil zone list” now handles empty zonelists.
• Enforcer: Unsigned comparison resulting in wrong error message.
• ods-ksmutil: fixed issue where first ds-seen command run on a zone would work, but return an error code and not send a HUP to the enforcerd.
• Signer Engine: A threading issue occasionally puts the default validity on NSEC(3) RRs and the denial validity on other RRs.
• Signer Engine: An update command could interrupt the signing process and the zone would get missing signatures.
• Signer Engine: Fix an issue where some systems could not copy the zone file.
• Zonefetcher: Check inbound serial in transferred file, to prevent redundant zone transfers.

Download the tarball from: opendnssec-1.3.1.tar.gz

• Can now read CKA_ALWAYS_AUTHENTICATE but does not use it.
• Encryption and decryption using CKM_RSA_PKCS.
• Support X.509 certificates. (Patch from Thomas Calderon)
• Updated backup instructions.
• Only a Security Officer can set CKA_TRUSTED to true.
• The softhsm tool can set the value of CKA_TRUSTED.
• Support Botan 1.10.0.
• Better signing performance with a single element cache for the PK_Signer object.
• Document README.MinGW describes how to build on Windows. (Text and patches contributed by Jaroslav Imrich)

Bugfixes:

• API changes in Botan created a namespace collision.
• API changes in Botan’s state handling.
• BigInt::to_u32bit was accidently dropped in Botan. Adding it as a compatibility function to SoftHSM.
• Better exception handling.
• CKF_USER_PIN_COUNT_LOW and CKF_SO_PIN_COUNT_LOW must be set if an incorrect PIN has been entered at least once.
• Windows: Detect LoadLibrary.
• Windows: Set CRYPTOKI_EXPORTS.
• Windows: Load library correctly in softhsm.
• Windows: Compatibility function for getpass.
• Windows: Use _putenv and not setenv.
• Windows: Generate the DLL file.
• Windows: The softhsm tool will use the DLL file by default.
• Windows: Log to EventLog.
• Windows: Fix parsing of configuration file.
• Windows: The check program now links with a shared libgcc in order to make the exceptions work.

Known issue:

• Firefox does improper setting of CKA_DERIVE attribute during PKCS#12 import. See https://bugzilla.mozilla.org/show_bug.cgi?id=515663

Download the tarball from: softhsm-1.3.0.tar.gz