It may well be the right thing to do. The implementation is certainly on par with jCIFS right now. The jCIFS implementer, in fact, has been reducing NTLM support in that library to bare minimum over time, because he has a for-profit venture to sell his "real" implementation. So, for instance, logic having to do with how to interpret flags etc. is no longer there.
Karl On Wed, Dec 12, 2012 at 6:45 AM, Oleg Kalnichevski <[email protected]> wrote: > Karl, > > If you are confident the internal NTLM engine implementation is on par > with JCIFS, feel free to rephrase the official NTLM guide [1] for the > coming releases. We should still have a section describing how to plug > in JCIFS if required, but I do not mind dropping recommendation to do > so, if you think it is the right thing to do. > > Cheers > > Oleg > > [1] http://hc.apache.org/httpcomponents-client-ga/ntlm.html > > > --------------------------------------------------------------------- > 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]
