summaryrefslogtreecommitdiff
path: root/net/powerdns/files
AgeCommit message (Collapse)AuthorFilesLines
2020-09-24net/powerdns: Update to 4.3.1otis1-2/+2
Security fix: * CVE-2020-17482: https://doc.powerdns.com/authoritative/security-advisories/powerdns-advisory-2020-05.html An issue has been found in PowerDNS Authoritative Server before 4.3.1 where an authorized user with the ability to insert crafted records into a zone might be able to leak the content of uninitialized memory. Such a user could be a customer inserting data via a control panel, or somebody with access to the REST API. Crafted records cannot be inserted via AXFR. Changelog: * New Features - Add ubuntu focal target * Improvements - EL8 pkgs: Build mysql backend against mariadb-connector-c-devel - gpgsql: Reintroduce prepared statements - gsqlite3backend: add missing indexes - Use real remote for supermaster createSlaveDomain() - Optimize IXFR-to-AXFR fallback path - Install bind SQL schema files as part of bindbackend - Do not send out of zone lookups to the backends * Bug Fixes: - Raise an exception on invalid hex content in unknown records. - Handle the extra single-row result set of MySQL stored procedures * pkgsrc-specific: - The default pid file patch in rc.d script has been fixed
2016-06-08Remove the stability entity, it has no meaning outside of an official context.jperkin1-1/+0
2016-06-08Change the service_bundle name to "export" to reduce diffs between thejperkin1-1/+1
original manifest.xml file and the output from "svccfg export".
2014-12-10Update PowerDNS to 3.4.1.fhajny1-0/+30
pkgsrc changes: - SQLite 2.x support no longer exists - SQLite 3.x support cannot be compiled outside the main package because of how symbols are distributed, so making it a compile time option for net/powerdns now. Too many changes since 2.9.22.5 (over 2 years ago), see the full changelog: http://doc.powerdns.com/md/changelog/ Upgrade notes: - PowerDNS 3.4 comes with a mandatory database schema upgrade coming from any previous 3.x release. - PowerDNS 3.1 introduces native SQLite3 support for storing key material for DNSSEC in the bindbackend. With this change, support for bind+gsql-setups ('hybrid mode') has been dropped. - PowerDNS 3.0 introduces full DNSSEC support which requires changes to database schemas. By default, old non-DNSSEC schema is assumed. Please see the docs on upgrading for particular steps that need to be taken: http://doc.powerdns.com/md/authoritative/upgrading/
2006-08-13Import net/powerdns, based on wip/pdns2 from pkgsrc-wip.ghen1-0/+19
The PowerDNS nameserver is a modern, advanced and high performance authoritative-only nameserver. It is written from scratch and conforms to all the relevant DNS standards documents. PowerDNS is open source. The PowerDNS nameserver utilizes a flexible backend architecture that can access DNS information from any data source. This includes file formats, Bind zone files, relational databases or LDAP directories. See the net/powerdns-* packages for additional backend modules.