#1193 SSH: Configure GlobalKnownHosts instead of UserKnownHosts
Closed: Fixed None Opened 12 years ago by sgallagh.

Right now, the sss_ssh_knownhostsproxy client pieces will update the users' ~/.ssh/sss_known_hosts file. But it makes more sense that we should have the SSH Responder update the /etc/ssh/sss_known_hosts file globally for the system instead.

This will accomplish several things:
1) It eliminates the risk of concurrent clients editing the hosts file because the Responder is serialized
2) It will reduce LDAP lookups in general, since multiple users will not need to look up the same hosts
3) It will reduce the scope of the client libraries to be more consistent with our other sss_client features.


Fields changed

owner: somebody => jcholast

Fields changed

rhbz: => 0

master: e6ab4b3[[BR]]
sssd-1-8: 56fb649

resolution: => fixed
status: new => closed

Metadata Update from @sgallagh:
- Issue assigned to jcholast
- Issue set to the milestone: SSSD SSH Cleanup

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2235

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata