Hi there,
Thanks for your feedback!
> Bear in mind, putting a password in an environment variable can be seen by
> other users on the same system with "ps auxwwe".
Sure. But in my scenario, the control host is considered a „safe“ developer
machine, while the target host is considered the
Hi there, hi past me,
> My (non-working) attempt:
> […]
> So it seems the "-l" is dropped into the void letting ssh assume USER was the
> target host? I don’t actually get what I can do.
Turns out, I have to write down the description of my issue and then send the
email before I magically
Hi everyone,
Thanks for all the ideas! Meanwhile, I’ve made some progress because there was
another answer on "ask ubuntu" that got absolutely no interaction but that is a
brilliant solution:
https://askubuntu.com/a/1263657 :
> just create a wrapper script for the ssh command.
> ssh_sudo:
> {
Hi Dan,
> Why not rsync directly as root? Then you can use a passwordless,
> passphraseless RSA (or similar) keypair.
That’s because these are cloud instances that get maintained by multiple
admins. If we require all of them to log in as root, we would have to share the
root password – and
Hi there,
We are using ansible to deploy system configuration and web application source
code to clusters of Linux computers. One part of this process requires
transferring large directories to the target hosts, which is done using the
„synchronize“ command in ansible that is in turn a wrapper
