summaryrefslogtreecommitdiff
path: root/src/resolve/resolved-manager.h
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2020-11-05 14:17:37 +0100
committerYu Watanabe <watanabe.yu+github@gmail.com>2020-12-03 07:25:17 +0900
commit90df0fbea893fb563876069f2b156256768197f8 (patch)
tree039df2b480efb08ecbb5c7db1b7402e6698d1ffe /src/resolve/resolved-manager.h
parentc8037dbf05da586b6a210ac04f145d99f424971f (diff)
downloadsystemd-90df0fbea893fb563876069f2b156256768197f8.tar.gz
resolved: automatically flush caches on clock change
DNSSEC validation takes the system clock into account to validate signatures. This means if we had incorrect time and the time is then changed to the correct one we should flush out everything and re-validate taking the new time into account. (This logic will also trigger after system suspend, which is not bad either, given that quite possibly we are connected to a different network, and thus would get different DNS data, without us noticing otherwise via link beat).
Diffstat (limited to 'src/resolve/resolved-manager.h')
-rw-r--r--src/resolve/resolved-manager.h4
1 files changed, 3 insertions, 1 deletions
diff --git a/src/resolve/resolved-manager.h b/src/resolve/resolved-manager.h
index 739683cbb5..120b63dc8c 100644
--- a/src/resolve/resolved-manager.h
+++ b/src/resolve/resolved-manager.h
@@ -143,6 +143,8 @@ struct Manager {
Hashmap *polkit_registry;
VarlinkServer *varlink_server;
+
+ sd_event_source *clock_change_event_source;
};
/* Manager */
@@ -188,7 +190,7 @@ void manager_dnssec_verdict(Manager *m, DnssecVerdict verdict, const DnsResource
bool manager_routable(Manager *m);
-void manager_flush_caches(Manager *m);
+void manager_flush_caches(Manager *m, int log_level);
void manager_reset_server_features(Manager *m);
void manager_cleanup_saved_user(Manager *m);