cc_staff
176
edits
Automation in the context of multifactor authentication: Difference between revisions
Jump to navigation
Jump to search
Automation in the context of multifactor authentication (view source)
Revision as of 20:49, 1 March 2024
, 8 months agono edit summary
No edit summary |
No edit summary |
||
| Line 63: | Line 63: | ||
{{Command|rsync -e "ssh -i .ssh/private_key_to_use" ...}} | {{Command|rsync -e "ssh -i .ssh/private_key_to_use" ...}} | ||
It's often much more convenient to put these parameters into your ~/.ssh/config file, so it gets picked up by any ssh client invocation. For instance: | |||
host robot | |||
hostname robot.cluster.alliancecan.ca | |||
user myrobot | |||
identityfile ~/.ssh/my-robot-key | |||
identitiesonly yes | |||
requesttty no | |||
this means that the following kinds of commands will do what you want: | |||
{{Command|ssh robot /usr/bin/ls}} | |||
{{Command|rsync -a datadir/a robot:scratch/testdata}} | |||
</translate> | </translate> | ||