Number of commits found XX: 16

dns/opendnssec2: Update to 2.1.7

Patches removed were incorporated upstream.

Changelog:	https://www.opendnssec.org/2020/10/opendnssec-2-1-7/

PR:		250293
Submitted by:	Jaap Akkerhuis <jaap@NLnetLabs.nl> (maintainer)
MFH:		2020Q4 (blanket: bugfix release)

Fix build with -fno-common

While here use INSTALL_TARGET=install-strip to install stripped binaries.

dns/opendnssec2: upgrade 2.1.4 -> 2.1.6

This release of 2.1.6 fixes some issues regarding the key list
wrongfully displayed (a regression bug in 2.1.5) as well as a small
leak in the enforcer (which can add up when you bang the enforcer
with a lot of commands. And as well as a serious signing error when
using Combined Signing Keys (CSKs), this is only relevant if you
combine KSK and ZSK in one. Especially users of CSKs need this fix
now. Another nice fix is a reconnect to a MySQL/MariaDB database
you you don't have to tweak database parameters.

PR:		244047
Submitted by:	Jaap Akkerhuis <jaap@NLnetLabs.nl> (maintainer)
Relnotes:	https://www.opendnssec.org/2019/11/opendnssec-2-1-5/
		https://www.opendnssec.org/2020/02/opendnssec-2-1-6/

dns/opendnsssec*: switch to openhsm2 to the HSM option.

Bump PORTREVISION on ldns consumers

Shared lib version changed in update

Reported by:	sunpoet

Update to 2.1.4

PR:		237988
Sponsored by:	Netzkommune GmbH

Update to 2.1.3:

As of today version 2.1.3 of OpenDNSSEC has been released. No special
migration steps are required when upgrading from a previous 2.x.x
release. It includes fixes to the build system, some regressions w.r.t.
OpenDNSSEC 1.4 and a signing bug. Please note that version 2.1.2 was
skipped for release.

Build fixes:

* OPENDNSSEC-904: autoconfigure fails to properly identify functions in
  ssl library on some distributions. This caused the "tsig unknown
  algorithm hmac-sha256" error.
* OPENDNSSEC-894: repair configuration script to allow excluding the
  build of the enforcer.

(Only the first 15 lines of the commit message are shown above )

* Bump Revision
* Fix typo in the Port's Makefile, causes a failure in a conversion script
* Added license file
* Cleanup Makefile

PR:		221144
Submitted by:	<jaap@NLnetLabs.nl> (maintainer)
Reviewed by:	matthew (mentor)
Approved by:	matthew (mentor)
MFH:		2017Q3
Differential Revision:	https://reviews.freebsd.org/D11898

Fix OPTIONS_DEFAULT: remove DOCS which is added by framework

Approved by:	portmgr (blanket)

dns/opendnssec2: update 2.1.0 -> 2.1.1

- OPENDNSSEC-889: MySQL migration script didnt work for all database
  and MySQL versions.
- OPENDNSSEC-887: Segfault on extraneous tag.
- OPENDNSSEC-880: Command line parsing for import key command failed.
- OPENDNSSEC-890: Bogus signatures upon wrong zone input when TTLs
  for same rrset are mismatching.

PR:		218995
Submitted by:	Jaap Akkerhuis <jaap@NLnetLabs.nl> (maintainer)

dns/opendnssec2: update 2.0.3 -> 2.1.0

- Fix DB scripts from docs

PR:		217563
Submitted by:	Jaap Akkerhuis <jaap@NLnetLabs.nl> (maintainer)
MFH:		2017Q1

- Chase ldns shlip bump

PR:		217495

dns/opendnssec2: update 2.0.1 -> 2.0.3

PR:		213610
Submitted by:	Jaap Akkerhuis <jaap@NLnetLabs.nl> (maintainer)
MFH:		2016Q4

dns/opendnssecs: Add SSL flags and honor them, configure SSL base too

Approved by:	SSL blanket

- Update to 2.0.1
- Switch to options helpers

This release is primarily focused on ironing out the issues on the migration
path from 1.4 to 2.0. Besides that there are no functional changes.


* Fixed crash and linking issue in ods-migrate.
* Fixed case where 2.0.0 could not read backup files from 1.4.10.
* Fixed bug in migration script where key state in the database wasn't
transformed properly.

PR:		211403
Submitted by:	Jaap Akkerhuis <jaap@NLnetLabs.nl> (maintainer)
Sponsored by:	DK Hostmaster A/S

The current opendnssec porthas seen a massive rewrite by the upstream
so it was rechristened opendnssec Version 2.
To quote the announcement at <https://www.opendnssec.org>:

"OpenDNSSEC got a entire re-write of the enforcer. This part of
OpenDNSSEC controls changing signing keys in the right way to perform
a roll-over. Before, the enforcer would perform a roll-over according
to a strict paradigm. One scenario in which deviations would not be
possible.

The new enforcer is more aware of the zone changes being propagated in
the Internet. It can therefore decide when it is safe to make changes,
rather than to rely upon a given scenario.

PR:		211018
Submitted by:	Jaap Akkerhuis <jaap@NLnetLabs.nl>
Sponsored by:	DK Hostmaster A/S

Number of commits found XX: 16

9 vulnerabilities affecting 70 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities

Last updated:
2021-01-26 20:33:26