-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to submit password with space in non-interactive mode #305
Comments
I think it relates not only to password but also user names, nicknames (for connections) and perhaps filenames for |
@snuyanzin, thanks for looking into this issue. Except quoting, is it possible to allow escaping some symbols, for example, allow also such cases: |
Current PR allows escaping of spaces like
In case there should be quote the other quotes could be used e.g.
The only issue could be if there is a need to have different types of quotes in a word. |
As we support more kinds of quoting people will be confused as to the semantics. I think it's time to state for the record that our goal is to be compatible with posix bash. (Single quotes, double quotes, back-slashes. Not back-quotes, braces, dollars etc.) |
Agree about posix for double quotes, back-slashes.
which should be equivalent to
? |
Currently added posix compatibility for double quotes and back-slashes |
Fixed in cc37485. Thanks for working on this! |
There is no way for specifying a password which contains space in non-interactive mode.
For example, without escaping, it is expected that it wouldn't work:
but it would be good to add a way for escaping the password:
Please note that password may be specified using env variable, so this use case may be more common.
As a side note, tools like
sshpass
allow these both variants of quoting the password.The text was updated successfully, but these errors were encountered: