Open a-tonchev opened 3 years ago
I can confirm the error
We've just managed to reproduce this using a password that contains a closing parenthesis ()
). I'll try to look into it next week. It seems we'll have to change our password escape strategy.
@nstCactus I tried it with alphanumeric password and it works. But I think it is quite good if we are not limited by that. The password that we used previously had no closing parenthesis, but other special characters, and still don't work.
While fixing this issue please try all the "regular" special characters (#!+^<>/%&$§()[]}{\?`´")
What do you think, when will you be able to fix this problem?
Thanks
Issue still exist in the current Version. @nstCactus did you have an Idea, how to fix that?
Sorry I didn't have the time to look into this and I can't give you an ETA. PRs are welcome though!
There is a kind of serious bug while using mode "synchronize",
at first the deployment fails, but it also creates a file in the directory with the characters from the command, including also the password:
I think it is caused because the password is wrapped with single quote, that will break the open single quote at --rsh
Using mode "archive" works like a charm.