To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=104417





------- Additional comments from [email protected] Thu Sep  3 07:23:21 +0000 
2009 -------
>Neon mailing list replies that NTLMv2 support is now ready for testing, for a
>planned 0.29.0 release.

 Well, it's not that easy... 

Neon 0.28 contains Windows-only NTLM support. Stuff is implemented using native
Windows API (-> SSPI). I have no insights into the neon SSPI implementation and
have no idea whether it supports v2 at all or is just buggy. As a matter of
fact, the behavior you noticed is caused by the SSPI stuff, because OOo 3.1 uses
the SSPI code. You should ask the submitter of the SSPI neon stuff for details.

Starting with 0.29, neon has a completely new NTLM implementation that should
work on all platforms, including Windows. This implementation comes with v2
support. I know this implementation "very well".  ;-)

Thus, starting with neon 0.29, for Windows one can choose between "SSPI" and
"NTLM" at neon compile time. For OOo (starting with 3.2) we will choose SSPI for
Windows, NTLM on all other platforms. Why? SSPI comes with a very important
feature that is currently missing in the NTLM implementation - the ability to
automatically to use the credentials of the currently logged in Windows user to
authenticate with Websites (-> e.g. SharePoint).

>(Is the listed contributor, 'Kai' == 'kso'? Thanks!)

 You're welcome. :-)

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to