Bug 211018

Summary:

[NEW PORT] dns/opendnssec2: Tool suite for maintaining DNSSEC

Product:

Ports & Packages

Reporter:

Jaap Akkerhuis <jaap>

Component:

Individual Port(s)

Assignee:

Erwin Lansing <erwin>

Status:

Closed FIXED

Severity:

Affects Many People

CC:

erwin

Priority:

---

Keywords:

feature, patch

Version:

Latest

Hardware:

Any

OS:

Any

Bug Depends on:

Bug Blocks:

211020

Attachments:

Description	Flags
Shar of new port	none

Description Jaap Akkerhuis 2016-07-11 21:49:56 UTC

Created attachment 172394 [details]
Shar of new port

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>:

<quote>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.
</quote>

Accompanying this new port there will be some changes to opendnssec (added conflict with this port) and opendnssec13 (adding conflict as well and setting Expire date).

These updates will submitted separately.

Comment 1 commit-hook freebsd_committer

2016-07-13 13:29:22 UTC

A commit references this bug:

Author: erwin
Date: Wed Jul 13 13:29:19 UTC 2016
New revision: 418476
URL: https://svnweb.freebsd.org/changeset/ports/418476

Log:
  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

Changes:
  head/dns/Makefile
  head/dns/opendnssec2/
  head/dns/opendnssec2/Makefile
  head/dns/opendnssec2/distinfo
  head/dns/opendnssec2/files/
  head/dns/opendnssec2/files/opendnssec.in
  head/dns/opendnssec2/files/pkg-message.in
  head/dns/opendnssec2/pkg-descr
  head/dns/opendnssec2/pkg-plist

Comment 2 Erwin Lansing freebsd_committer

2016-07-13 13:29:49 UTC

Committed, thanks!