> The way I read the SSH responder, calling
> sysdb_update_ssh_known_host_expire() would be the right thing to do, but
> I wonder if that would be enough or whether we'd need to call out to the
> ssh responder to force writing out a new hosts file.
What you want to do is remove the entry from the cache, right? If so,
then sysdb_update_ssh_known_host_expire() is not the right thing to call.
What is the right thing to call? I would like to be able to expire
either a single host or all hosts ...
Why do you want to force writing out a new hosts file? The file should
never be used without sss_ssh_knownhostsproxy, which already takes care
of rewriting it.
Okay, that's good to know. I'll assume it's re-written every time it's