Closed hongxuchen closed 4 weeks ago
Hello @hongxuchen, how would you correct the comments in the cntlm.conf
?
@fralken I prefer to provide more valid configuration examples in the comments, especially for those necessary options like Password; for the comprehensive usage, it's better to direct users to the man page or online documentation. For Password, I suggest:
No URL escape encoding is needed. For example,
123@xyz
is parsed literally, do not use123%40xyz
where%40
is the encoding of@
. In case the password contains special characters like spaces(`), pound signs(
#), etc, it should be enclosed in double quotes ("). For examples,
123#xyzshould be
"123#xyz"`. See cntlm's man page for more details.
Hello @hongxuchen, would you like to prepare a PR with this change?
Hello @hongxuchen, would you like to prepare a PR with this change?
PR added
thanks! fixed by #117
In the default cntlm.conf, there are comments like:
Despite that it is true there is no need to use URL escape characters (e.g.,
, which is mentioned clearly in cntlm's man page.
%40
for@
), it is however needed to double quote some special characters like#
,;
,Therefore when password contains some special characters like
#
,;
, it will ignore the subsequent characters afterwards. SoPassword XXX#YYY
will be treated asPassword XXX
; and the correct configuration isPassword "XXX#YYY"
.