Try surrounding the password with *single* quotes.
And what if the password contains a single-quote and a double-quote, like this: 123"4'56 ?
This isn't a Collaborator problem . . . it is a Windows CMD shell problem. You will have a problem with other characters as well (like caret ^ and ampersand & and percent %). There doesn't seem to be a simple clean way to do this.
A command line with arguments is not necessarily executed in a cmd.exe window where escaping restrictions apply for & % ^ " etc.
I can execute the ccollab.exe login command with Win32 API functions or with C# process launching functions, or with Python or Java.
In these languages, no escaping restrictions are necessary, except those required by the language and the use of two double-quotes for escaping a single double-quote inside an argument.
Because the arguments are always (normally?) passed to executables surrounded by double-quotes, aren't they?
What are the new rules of passing arguments to the ccollab.exe login command in Collaborator since 13.2?
I think it is Collaborator's responsibility to define the rules of passing arguments to its commands.
