On Tue, 10 Dec 2013, Daniel Stenberg wrote:

> > after update from curl-7.30.0 to curl-7.31.0 not work ftp with
> > password containing letter `;' - semicolon. I was try use
> > curl-7.33.0, but with the same result.
>
> I'm taking this over here from the users list. (also filed as bug
> #1311)
>
> I think we should do something about the ; as separator even if
> it means breaking how users may have started to use 7.31-7.33,
> due to how it breaks compatibility with older libcurls and
> semicolons in passwords.
>
> I suggest we either remove the ability to add options to that string,
> or make the separator something that is less likely to be used in a
> password. Like for example having it the spelled out ";options=" or
> something.

I'm not a fan of the latter as that would require the user to perform the
following in order to specify the authentication type in the email
protocols:

user:password;options=auth=NTLM

At present the options are only used in the email protocols, although I
would like to extend them to other protocols. Not only that but multiple
authentication mechanisms in the options is also on my to do list as well.
For example:

user:password;auth=NTLM;auth=CRAM-MD5;auth=LOGIN

I can't remember which user and password options allow URL encoded colons at
present, and I know this is something that we talked about before, but could
we consider adding support for URL encoding these separator characters in
the CURLOPT_USERPWD?

That way it a) solves this issue and b) solves previously discussed issues
with having a colon in user names and c) provides consistency across all
user/password options ;-)

Kind Regards

Steve
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2013-12-10