hopefully also understand the workings of the Domain Name System. When used to
check an domain (aka zone) is submitted to DNSCheck, it will investigate the
general health by performing various tests and sanity checks.
WWW: http://dnscheck.iis.se/
PR: ports/148370
Submitted by: dnscheckengine-port at academ.com (Stan Barber)
Approved by: tabthorpe (mentor)
- connect to license framework
- add special patch from glarkin to ensure daemon detach from tty,
change some printf to use the warning function instead.
PR: 148586
Submitted by: Chris Howey <howeyc _at_ gmail.com>
Approved by: maintainer, glarkin (mentor)
If a query is made explicitly for a record of type 'RRSIG' to a validating
recursive server running BIND 9.7.1 or 9.7.1-P1, and the server has one or
more trust anchors configured statically and/or via DLV, then if the answer
is not already in cache, the server enters a loop which repeatedly generates
queries for RRSIGs to the authoritative servers for the zone containing the
queried name.
CVE: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-0213
CERT: http://www.kb.cert.org/vuls/id/211905
Versions affected: 9.7.1, 9.7.1-P1
Severity: High
Exploitable: remotely
http://www.isc.org/software/bind/advisories/cve-2010-0213
code where the 9.7.x series tightened its adherence to the DNS protocol
as written, vs. the 9.6.x series which was more liberal in what it accepted.
Specifically:
1. Restore processing of certain forms of negative responses that do
not contain all of the required elements to avoid aggressive
re-querying of authority servers.
2. Accept answers from authority servers without the AA bit set
if they meet the other requirements of an answer packet.
More detail can be found here:
https://www.isc.org/community/blog/201007/compatibility-issues-bind-970-and-971
(QNAME,QTYPE) by prespecified answers. This class is to be used in test suites
where you want to have servers to show predefined behavior.
If the server will do a lookup based on QNAME,QTYPE and return the specified
data. If there is no QNAME, QTYPE match the server will return a SERVFAIL.
A log will be written to STDERR it contains time, IP/PORT, QNAME, QTYPE, RCODE.
WWW: http://search.cpan.org/dist/Net-DNS-TestNS/
PR: ports/148161
Submitted by: Sunpoet Po-Chuan Hsieh <sunpoet@sunpoet.net>
Feature safe: yes
fix was too hasty. Employ a more robust fix that removes the _perl_ dep for
both this file and bind9.xsl.h. The pre-generated versions of these files
are identical to the newly generated ones, which is why this perl issue
never came up previously.
I still have reservations about baking the ISC DLV key into named, but given
that this was already done in 9.7.0+ at least this way we don't violate POLA.
which is a problem, however what it's doing is baking the ISC
DLV key into named which is not something I think is reasonable
to do by default.
So, instead of adding perl as a build dependency eliminate the
need for the file altogether.
This version has numerous minor bug fixes, please refer to the
CHANGES file for details. Many (but not all) of the fixes are
DNSSEC-related, and all users who are doing DNSSEC validation
are encouraged to upgrade to this version.
This release was inadvertently dubbed 2.54 in its logging by Simon Kelley,
so adjust our PORTVERSION to match that, but still build the 2.53 tarball.
Simon will treat 2.53 and 2.54 the same and release 2.55 next time.
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2010q2/004105.html
Check work/dnsmasq-2.53/src/config.h for VERSION after "make extract" to see.
Approved by: garga (mentor)
- actually pass the options-enabled arguments to the configure script!
- add the "hide symbols" configurable knob, though I've no idea why
anybody would want to turn that off... except maybe for debugging
- install the "acountry", "adig", and "ahost" programs, since they do
come in useful every now and then
- refresh the patches and add descriptions at the top
related to the handling of broken DNSSEC trust chains.
This fix is only necessary for those who have DNSSEC validation
enabled and configure trust anchors from third parties, either
manually, or through a system like DLV.
security patches to the 9.6.1 version, as well as many other bug fixes.
Due to the fact that the DNSSEC algorithm that will be used to sign the
root zone is only included in this version and in 9.7.x those who wish
to do validation MUST upgrade to one of these prior to July 2010.
Feature safe: yes
asynchronously. It is an asynchronous wrapper around getaddrinfo(3),
getnameinfo(3), res_query(3) and res_search(3) from libc and libresolv.
In contrast to GNU's asynchronous name resolving API getaddrinfo_a(),
libasyncns does not make use of UNIX signals for reporting completion of name
queries. Instead, the API exports a standard UNIX file descriptor which may be
integerated cleanly into custom main loops.
In contrast to asynchronous DNS resolving libraries like libdenise, skadns,
adns, libasyncns is just an asynchronous wrapper around the libc's synchronous
getaddrinfo() API, which has the advantage of allowing name resolution using
techniques like Multicast DNS, LDAP or NIS using standard libc NSS (Name
Service Switch) modules. libasyncns is compatible with IPv6 if the underlying
libc is.
libasyncns is very tiny, consisting of just one header and one source file. It
has no dependencies besides libc.
WWW: http://0pointer.de/lennart/projects/libasyncns/
from ISC. It has numerous bug fixes compared to 9.4.3*, however
in the case of this version "extended" only applies till 2010/12/31
so serious BIND users are still encouraged to upgrade to 9.6.x.
child processes must not shutdown() their sockets
* Fixes and reports a problem occuring with jumping system time,
as reported when running inside some virtual machine. Time jumps
are reported to the log with loglevel NOTICE.
* Delegation now has precedence over wildcard matching
Thanks to Fab for the fix
Fixes bugs #0000038, #0000042
PR: 143223
Submitted by: Hung-Yi Chen <gaod@hychen.org> (maintainer)
Update to new upstream release 2.52. Changelog excerpt below the approval.
Approved by: miwi (mentor)
Upstream changelog excerpt (omitting Linux, Solaris and MacOS X specifics):
[...] Re-read the set of network interfaces when re-loading /etc/resolv.conf
if --bind-interfaces is not set. This handles the case that loopback
interfaces do not exist when dnsmasq is first started.
Tweak the PXE code to support port 4011. This should reduce broadcasts and
make things more reliable when other servers are around. It also improves
inter-operability with certain clients.
Make a pxe-service configuration with no filename or boot service type legal:
this does a local boot. eg. pxe-service=x86PC, "Local boot"
Be more conservative in detecting "A for A" queries. Dnsmasq checks if the
name in a type=A query looks like a dotted-quad IP address and answers the
query itself if so, rather than forwarding it. Previously dnsmasq relied in
the library function inet_addr() to convert addresses, and that will accept
some things which are confusing in this context, like 1.2.3 or even just
1234. Now we only do A for A processing for four decimal numbers delimited by
dots.
[...]
Increased the default limit on number of leases to 1000 (from 150). This is
mainly a defence against DoS attacks, and for the average "one for two class
C networks" installation, IP address exhaustion does that just as well.
Making the limit greater than the number of IP addresses available in such an
installation removes a surprise which otherwise can catch people out.
Removed extraneous trailing space in the value of the DNSMASQ_TIME_REMAINING
DNSMASQ_LEASE_LENGTH and DNSMASQ_LEASE_EXPIRES environment variables. Thanks
to Gildas Le Nadan for spotting this.
Provide the network-id tags for a DHCP transaction to the lease-change script
in the environment variable DNSMASQ_TAGS. A good suggestion from Gildas Le
Nadan.
Add support for RFC3925 "Vendor-Identifying Vendor Options". The syntax looks
like this:
--dhcp-option=vi-encap:<enterprise number>, .........
Add support to --dhcp-match to allow matching against RFC3925
"Vendor-Identifying Vendor Classes". The syntax looks like this:
--dhcp-match=tag,vi-encap<enterprise number>, <value>
Add some application specific code to assist in implementing the Broadband
forum TR069 CPE-WAN specification. The details are in contrib/CPE-WAN/README
Increase the default DNS packet size limit to 4096, as recommended by RFC5625
section 4.4.3. This can be reconfigured using --edns-packet-max if needed.
Thanks to Francis Dupont for pointing this out.
Rewrite query-ids even for DNSSEC signed packets, since this is allowed by
RFC5625 section 4.5.
[...]
Fix link error when including Dbus but excluding DHCP.
Thanks to Oschtan for the bug report.
Updated French translation. Thanks to Gildas Le Nadan.
Updated Polish translation. Thanks to Jan Psota.
Updated Spanish translation. Thanks to Chris Chatham.
DNSSEC. It secures zone data just before it is published in an
authoritative name server.
WWW: http://www.opendnssec.org
PR: ports/142103
Submitted by: Jaap Akkerhuis <jaap@NLnetLabs.nl>
to thoroughly test this version before updating production systems.
For the port, introduce a new dependency, security/p5-Digest-SHA
Changes in this version, in addition to numerous minor bug fixes:
Feature: Truncation for Nameserver
TAKE CARE:
this feature may cause unexpected behavior for your nameservers
Net::DNS::Packet::truncate is a new method that is called from
within Net::DNS::Nameserver that truncates a packet according to
the rules of RFC2181 section 9.
Feature: Added Net::DNS::Domain
Net::DNS::Domain is an attemt to consistently approach the various
ways we interface with what RFC 1035 calls <domain-name>.
Feature: KX RR
Added support for the KX RR, RFC2230
Feature: HIP RR
Added support for the HIP RR, RFC5205
Feature: DHCID RR
Added rudimentary support for the DHCID RR.
Fix improved fuzzy matching of CLASS and TYPE in the Question
constructor method.
Fix AAAA dynamic update
PR: ports/136065 ports/127469
Submitted by: N.J. Mann <njm@njm.me.uk> and Aldis Berjoza <killasmurf86@gmail.com>
- Early identify port CONFLICTS
PR: 137855
Submitted by: Piotr Smyrak <smyru@heron.pl>
- Add --no-same-permissions to the EXTRACT_AFTER_ARGS command.
Tijl Coosemans has been reported an issue that when root is extracting from the
tarball, and the tarball contains world writable files
(sysutils/policykit as an example), there is a chance that the files
gets changed by malicious third parties right after the extraction,
which makes it possible to inject code into the package thus compromise
the system.
Submitted by: Tijl Coosemans <tijl@coosemans.org> Xin LI (delphij@)
- Fix some whitespaces
Tested with: exp-run
is designed to help you as a user determine what name services
are the best to use for an individual machine.
WWW: http://namebench.googlecode.com/
PR: ports/141202
Submitted by: Sahil Tandon <sahil at tandon.net>
e-mail addresses from the pkg-descr file that could reasonably
be mistaken for maintainer contact information in order to avoid
confusion on the part of users looking for support. As a pleasant
side effect this also avoids confusion and/or frustration for people
who are no longer maintaining those ports.
start testing it sooner rather than later. When the final version
is released the -devel will be removed.
Some of the new features of BIND 9.7.x are:
- Fully automatic signing of zones by "named"
- Simplified configuration of DNSSEC Lookaside Validation (DLV)
- Simplified configuration of Dynamic DNS, using the "ddns-confgen"
command line tool or the "local" update-policy option
- New named option "attach-cache" that allows multiple views to
share a single cache
- DNS rebinding attack prevention
- New default values for dnssec-keygen parameters
- Support for RFC 5011 automated trust anchor maintenance
(see README.rfc5011 for additional details)
- Smart signing: simplified tools for zone signing and key
maintenance
- Improved PKCS#11 support
Subsequently installing the package will result in a plist entry to remove a
directory that does not exist
So, change @dirrm to @dirrmtry to make them both happy.
this is designed to fix is related to DNSSEC validation on a resolving
name server that allows access to untrusted users. If your system does
not fall into all 3 of these categories you do not need to update
immediately.
