#1184 SSH: Continue connecting after sss_ssh_get_pubkeys failure in sss_ssh_knownhostsproxy
Closed: Fixed None Opened 12 years ago by jcholast.

Not doing so breaks ssh if it is configured to use sss_ssh_knownhostsproxy and SSSD service is not running or an error occured.


Fields changed

milestone: NEEDS_TRIAGE => SSSD SSH Cleanup

Fields changed

rhbz: => 0

Fields changed

priority: critical => blocker

Sorry, changed the wrong bug. Reverting to critical.

component: SSSD => SSH Keys
priority: blocker => critical

master: 1e68ae2[[BR]]
sssd-1-8: 4ffd160

resolution: => fixed
status: new => closed

Metadata Update from @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/2226

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