Re: [Sshpass-devel] Option for reading from arbitrary environment variable

[Chris B. <chr...@gm...>]

Understood! I guess my other thought had been that if I were to attempt
something like sshpass from scratch, I would personally consider flexible
environment variable names to be more generic and useful than using a fixed
name (just like using flexible file names is more generic and useful than
using a fixed file location); although I'm sure there are arguments to the
contrary. It's not like the current design has been limiting the tool's
usefulness or popularity, of course!

Thanks for getting round to reviewing this.

On Mon, 12 Jul 2021 at 18:40, Shachar Shemesh <sh...@sh...> wrote:

> On 12/07/2021 17:51, Chris Barnes wrote:
> > My initial use case was rsync proxyjumping through another server,
> > both of which need passwords (in my case, the gateway disallows key
> > logins and doesn't pass keys over to the next server). It was
> > convenient to load the password(s) from a .env file rather than typing
> > them myself and having them in the shell history.
> >
> I think the use case you describe falls under the same hospice as the
> answer I gave Denise. If I accept your patch (or the feature under any
> other name), then you'd end up running two nested instances of sshpass.
> I think it makes more sense for sshpass to be able to generically handle
> more than one password prompt. That would solve the problem without
> introducing specialized features into sshpass.
>
> Shachar
>
>
>