mirror of
https://github.com/NLnetLabs/unbound.git
synced 2026-01-28 01:19:19 -05:00
- patch suggested by Debian lintian: allow to -> allow one to, from
A. Schulze. git-svn-id: file:///svn/unbound/trunk@4567 be551aaa-1e26-0410-a405-d3ace91eadb9
This commit is contained in:
parent
980711e658
commit
babe659a64
2 changed files with 3 additions and 1 deletions
|
|
@ -2,6 +2,8 @@
|
|||
- Fixed contrib/fastrpz.patch, even though this already applied
|
||||
cleanly for me, now also for others.
|
||||
- patch to log creates keytag queries, from A. Schulze.
|
||||
- patch suggested by Debian lintian: allow to -> allow one to, from
|
||||
A. Schulze.
|
||||
|
||||
6 March 2018: Wouter
|
||||
- Reverted fix for #3512, this may not be the best way forward;
|
||||
|
|
|
|||
|
|
@ -1620,7 +1620,7 @@ but do not want to advertise over \fBdnscrypt\-provider\fR's TXT record certs
|
|||
distribution.
|
||||
A typical use case is when rotating certificates, existing clients may still use
|
||||
the client magic from the old cert in their queries until they fetch and update
|
||||
the new cert. Likewise, it would allow to prime the new cert/key without
|
||||
the new cert. Likewise, it would allow one to prime the new cert/key without
|
||||
distributing the new cert yet, this can be useful when using a network of
|
||||
servers using anycast and on which the configuration may not get updated at the
|
||||
exact same time. By priming the cert, the servers can handle both old and new
|
||||
|
|
|
|||
Loading…
Reference in a new issue