mc0e

Results 39 comments of mc0e

@maddes-b said: > Have a look at my fork at https://github.com/maddes-b/ssh-ident > There I extended ssh-ident to recognize ssh-agent/ssh-add and add a virtual paramter `-i ` Is that a work-in-progress...

> Accessing the ssh-agent of an identity can be done by just sourcing the related environment file of the wanted identity. > Same as using pure ssh-agent where you also...

I've also tried using an alias: ``` $ alias rsync='BINARY_SSH=/usr/bin/rsync $HOME/src/ssh-ident/ssh-ident' ``` and I've tried using a script at $HOME/bin/rsync: ``` #!/bin/bash BINARY_SSH=/usr/bin/rsync /home/mc0e/src/ssh-ident/ssh-ident "$@" ``` I get the same...

rsync uses ssh for its transport by default, and that can be configured explicitly using the `-e` option to rsync. ssh options should not ever be passed as arguments to...

It appears that the README should not recommend: ``` alias rsync='BINARY_SSH=rsync /path/to/ssh-ident' ``` I suspect that should be something along the lines of: ``` alias rsync='rsync -e "BINARY_SSH=ssh /path/to/ssh-ident"' ```...

That's not enough to make it work: ``` $ alias rsync='rsync -e "/home/mc0e/src/ssh-ident/ssh-ident"' $ rsync /tmp/foo example.org:/tmp/foo ssh-ident found '/home/mc0e/bin/ssh' as the next command to run. Based on argv[0] (/home/mc0e/src/ssh-ident/ssh-ident),...

Also, won't a random user id create problems with access to files in volumes written by a different user id?

There probably wants to be a check for presence of `sudo` also. It's very widespread, but not universal.

If I pipe the output of the `get-chaplocal` task to a file, and edit it to have `sudo` in front of the two docker commands, before running it through the...