trust-anchor-file, auto-trust-anchor-file, trust-anchor

Hi Ed - I currently maintain the Unbound package for LEDE / OpenWrt. On LEDE 17.01 we have Unbound configured to not only use RFC5011, but we have some scripting to keep it from cooking through flash. Unbound is rather busy maintaining the key, so we let it spin its wheels on tmpfs (mounted

Re: [Ext] Re: trust-anchor-file, auto-trust-anchor-file, trust-anchor

On 2/24/17, 13:07, "Robert Edmonds" wrote: ... the upstream for RHEL) you'd probably be covering 80-90% or so of the Linux distributions by usage. ... Thanks...I was waiting to see if any of the other 20-10% spoke up. ;) smime.p7s Description: S/MIME cryptographic

Re: trust-anchor-file, auto-trust-anchor-file, trust-anchor

Edward Lewis via Unbound-users wrote: > Is the use of trust-anchor-file for the public root zone KSK popular? Do > folks use it much at all (regardless of zone)? The same for trust-anchor > statements, which appear to be in-line of the configuration file. Hi, Ed: We ship the Debian package

trust-anchor-file, auto-trust-anchor-file, trust-anchor

>From reading the documentation, the difference between trust-anchor-file and >auto-trust-anchor-file is that the former is manually managed, the latter open >to Automated Updates (RFC 5011) management - is that correct? Is the use of trust-anchor-file for the public root zone KSK popular? Do