remote_exec: make keys from ~/.ssh work automatically
ClosedPublic

Authored by kparal on Aug 25 2015, 3:14 PM.

Details

Summary

If we hardcode some file name in our config file as ssh_privkey, it
crashes hard when the file does not exist, and also it precludes
paramiko's automatic ssh key lookup to kick in. We should use empty path
by default, so that users can store their keys in ~/.ssh as they are
used to and everything just work automatically. If they need to store
the key elsewere, they can use --ssh-privkey on CLI or ssh_privkey in
config.

This resolves audit
https://phab.qadevel.cloud.fedoraproject.org/rLTRN82d0e32a8d69d561e78c5da65c14cc7f74814626
.

Test Plan

Tested manually, keys in ~/.ssh work perfectly now. You can also specify an external key, works.

Diff Detail

Repository
rLTRN libtaskotron
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
kparal retitled this revision from to remote_exec: make keys from ~/.ssh work automatically.Aug 25 2015, 3:14 PM
kparal updated this object.
kparal edited the test plan for this revision. (Show Details)
kparal added reviewers: tflink, lbrabec, jskladan, mkrizek.
tflink accepted this revision.Aug 25 2015, 3:36 PM
This revision is now accepted and ready to land.Aug 25 2015, 3:36 PM
This revision was automatically updated to reflect the committed changes.