- Use INSTALL_MAN for the man files and respect NO_INSTALL_MANPAGESÂ knob
- Use INSTALL_DATA for PORTDOCS file
- Hide post-extract and post-patch procedure
- Bump PORTREVISION
PR: ports/163942 [1]
Submitted by: Garrett Cooper <yanegomi AT gmail.com> [1]
Approved by: maintainer via private mail
stay as a -devel until it's formally released, which should be soon'ish.
BIND 9.9 includes a number of changes from BIND 9.8 and earlier releases,
including:
NXDOMAIN redirection
Improved startup and reconfiguration time, especially with large
numbers of authoritative zones
New "inline-signing" option, allows named to sign zones completely
transparently, including static zones
Many other new features, especially for DNSSEC
See the CHANGES file for more information on features.
https://kb.isc.org/article/AA-00592
ports use BUILD_DEPENDS:= ${RUN_DEPENDS}. This patch fixes ports that are
currently broken. This is a temporary measure until we organically stop using
:= or someone(s) spend a lot of time changing all the ports over.
Explicit duplication > := > = and this just moves ports one step to the left
Approved by: portmgr
and generally improve the script (most of which was unneeded).
While I'm here, fix some other problems with the port:
1. Remove a dead MASTER_SITE
2. Make the rc.d script honor PREFIX
3. Install a link for /usr/local/bin/dnscheck-dispatcher so that
the rc.d script has something to start
Bump PORTREVISION due to package changes
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
APIs (libraries) for application developers to make softwares
IDNA2008-compliant, and also provides tools for system administrators
to process IDNs appropriately according to IDNA2008 specification.
The idnkit-2 is a toolkit revised by JPRS from the idnkit-1.0
developed by JPNIC, and it is released as an open source
free software modified to comply with IDNA2008.
idnkit-2 consists from its main part written in C and additional
API packages for other languages (Java, Python, and Perl).
WWW: http://jprs.co.jp/idn/index-e.html
PR: ports/162521
Submitted by: Rafal Lesniak <fbsd@grid.einherjar.de>
Feature safe: yes
following DDOS bug:
Recursive name servers are failing with an assertion:
INSIST(! dns_rdataset_isassociated(sigrdataset))
At this time it is not thought that authoritative-only servers
are affected, but information about this bug is evolving rapidly.
Because it may be possible to trigger this bug even on networks
that do not allow untrusted users to access the recursive name
servers (perhaps via specially crafted e-mail messages, and/or
malicious web sites) it is recommended that ALL operators of
recursive name servers upgrade immediately.
For more information see:
https://www.isc.org/software/bind/advisories/cve-2011-tbd
which will be updated as more information becomes available.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4313
Feature safe: yes
APIs (libraries) for application developers to make softwares
IDNA2008-compliant, and also provides tools for system administrators
to process IDNs appropriately according to IDNA2008 specification.
The idnkit-2 is a toolkit revised by JPRS from the idnkit-1.0
developed by JPNIC, and it is released as an open source
free software modified to comply with IDNA2008.
idnkit-2 consists from its main part written in C and additional
API packages for other languages (Java, Python, and Perl).
WWW: http://jprs.co.jp/idn/index-e.html
PR: ports/162520
Submitted by: Rafal Lesniak <fbsd@grid.einherjar.de>
Feature safe: yes
