Sorry for the delay...

2011/8/26 Steve Holme wrote:

> How would you like me to proceed with this, [...]

You will surely have noticed that the NTLM code has been reorganized
into something which will better resist future expansion and reuse.
And as of today you will most probably also be familiar with new
layout.

I would also like to have the SMTP/IMAP/POP3 authentication stuff
refactored out from protocol specific source code files into a
'nearly' protocol agnostic source code file. But given the details
that need to be addressed, this is something that has to be done out
of feature freeze period, and additionally I've run out of refactoring
energy for some time.

Relative to the ability to allow the user to choose not to send the
initial-response along with the authenticate command...

Have you come across a server which goes crazy if the initial-response
is provided on the same line as the authenticate command respecting
max command line size?

I'm asking this for the simple reason that if we expose this
capability, it has to be implemented and work the same with all
authentication mechanisms which support sending an initial-response
along with the authenticate command. Otherwise it would be a rather
broken capability flag that would fool user into believing that it
works where it should.

I'm not against allowing the existence of CURL_SASL_AUTH_NO_IR bit,
what I'm saying is that if it exists it must at least work with all
SASL mechanisms.

It is actually a feature on its own. And as such, it deserves its own
patch no matter if the feature is introduced before or after allowing
NTLM for SMTP and other protocols.

Thanks for your patience,

-- 
-=[Yang]=-
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html