| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
All checksums have been double-checked against existing RMD160 and
SHA512 hashes
Not committed (merge conflicts...):
net/radsecproxy/distinfo
The following distfiles could not be fetched (fetched conditionally?):
./net/citrix_ica/distinfo citrix_ica-10.6.115659/en.linuxx86.tar.gz
./net/djbdns/distinfo dnscache-1.05-multiple-ip.patch
./net/djbdns/distinfo djbdns-1.05-test28.diff.xz
./net/djbdns/distinfo djbdns-1.05-ignoreip2.patch
./net/djbdns/distinfo djbdns-1.05-multiip.diff
./net/djbdns/distinfo djbdns-cachestats.patch
|
|
|
|
Problems found with existing digests:
Package haproxy distfile haproxy-1.5.14.tar.gz
159f5beb8fdc6b8059ae51b53dc935d91c0fb51f [recorded]
da39a3ee5e6b4b0d3255bfef95601890afd80709 [calculated]
Problems found locating distfiles:
Package bsddip: missing distfile bsddip-1.02.tar.Z
Package citrix_ica: missing distfile citrix_ica-10.6.115659/en.linuxx86.tar.gz
Package djbdns: missing distfile djbdns-1.05-test25.diff.bz2
Package djbdns: missing distfile djbdns-cachestats.patch
Package djbdns: missing distfile 0002-dnscache-cache-soa-records.patch
Package gated: missing distfile gated-3-5-11.tar.gz
Package owncloudclient: missing distfile owncloudclient-2.0.2.tar.xz
Package poink: missing distfile poink-1.6.tar.gz
Package ra-rtsp-proxy: missing distfile rtspd-src-1.0.0.0.tar.gz
Package ucspi-ssl: missing distfile ucspi-ssl-0.70-ucspitls-0.1.patch
Package waste: missing distfile waste-source.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
|
|
|
|
=============
Some extracts from the git log:
* Add new DNSKEY algorithms registered by IANA
* Add AUTH checking over both UDP and TCP. [Fixes #80]
* New queue dispatch
* Clean out dead code, add tests to new code and add log entries.
[Closes #89]
* Log when an AS prefix is discarded
* Add simple command-line tool to add domains to the dispatcher queue
* Add callback functionality to logger
* Perl 5.18 fix (hash key order randomization)
* The authoritative servers for ARPA are the root servers, which caused
problems for our parent-finding algorithm. Worked around by special
-casing so that single-label names always return root as the parent.
[Closes #92]
* Make allowed maximum NSEC3 iterations a policy parameter
* Detect DNSCurve-supporting nameservers
* Significant improvements to glue checking
* Fix for referral check under undelegated
* More tests for new glue-checking code
* Detect names in domains reserved by IANA (RFC 6761). [Closes #96]
* Log messages for reserved ASs. [Closes #97]
|
|
=====================================
* Minimum required Perl version is now 5.10.1.
* A couple of new tests:
- That a minimal referral can fit in a 512-octet packet.
- The responses come from the same IP address the question was sent to.
- That NSEC or NSEC3 is used in signed zones.
- That NSEC3 parameters are sane.
- That RRSIG durations are sane.
* CZNIC contributed a Czech translation.
* Reserved IP ranges updated according to new RFCs.
* All tests that made SMTP connections have been removed.
* The CLI script has a --level flag to specify the lowest log level you want printed.
* A new, better algorithm to check nameserver AS distribution.
* Plus of course bug and stability fixes.
Release Notes for DNSCheck Lib v1.3.0
=====================================
Notable changes:
* The configuration file layout has changed completely!
Instead of the old, complicated variant, default configuration, default
policy and language files are now installed in the proper place in the Perl
module tree. The user should never need to care exactly where that is. Local
changes to the configuration now lives in /etc/dnscheck/config.yaml and
/etc/dnscheck/policy.yaml
You have to manually move and rename your old site_config.yaml and
site_policy.yaml, if you have them!
|
|
hopefully also understand the workings of the Domain Name System, DNS.
When a domain (aka zone) is submitted to DNSCheck it will investigate
the domain's general health by traversing the DNS from root (.) to
the TLD (Top Level Domain, like .SE) to eventually the nameserver(s)
that holds the information about the specified domain (like iis.se).
Some other sanity checks, for example measuring host connectivity,
validity of IP-addresses and control of DNSSEC signatures
will also be performed.
|
