diff options
| author | Lennart Poettering <lennart@poettering.net> | 2016-01-04 20:38:21 +0100 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2016-01-04 22:42:10 +0100 |
| commit | 0c8570287400ba57d3705a2f62dd26039121ea6f (patch) | |
| tree | 55c02b67868d1777fec53bd476ce52d8e403d496 /test/test-execute/exec-privatenetwork-yes.service | |
| parent | 85aeaccc10b111e8d16d3879b7c30a219ee6e10a (diff) | |
resolved: partially implement RFC5011 Trust Anchor support
With this patch resolved will properly handle revoked keys, but not
augment the locally configured trust anchor database with newly learned
keys.
Specifically, resolved now refuses validating RRsets with
revoked keys, and it will remove revoked keys from the configured trust
anchors (only until reboot).
This patch does not add logic for adding new keys to the set of trust
anchors. This is a deliberate decision as this only can work with
persistent disk storage, and would result in a different update logic
for stateful and stateless systems. Since we have to support stateless
systems anyway, and don't want to encourage two independent upgrade
paths we focus on upgrading the trust anchor database via the usual OS
upgrade logic.
Whenever a trust anchor entry is found revoked and removed from the
trust anchor a recognizable log message is written, encouraging the user
to update the trust anchor or update his operating system.
Diffstat (limited to 'test/test-execute/exec-privatenetwork-yes.service')
0 files changed, 0 insertions, 0 deletions