Support extended security for NTLMv2

Current Situation

• YADE supports NTLMv1 by use of the setting jcifs.smb.client.useExtendedSecurity=false
• This setting prevents use of NTLMv2

Desired Behavior

• YADE should not limit use of NTLM to a specific version NTLMv1, NTLMv2 etc.
• YADE should allow to specify a Java property file for SMB/CIFS authentication with NTLMv2 or newer where <filename.prp> is the path to the Java property file:
  • This feature is provided by YADE-399
  • Example
    • Windows: set JAVA_OPTIONS=-Djcifs.properties=<filename.prp>
    • Unix: export JAVA_OPTIONS=-Djcifs.properties=<filename.prp>
  • Available properties: Setting Client Properties

Workaround
If you get the error

jcifs.smb.client.useExtendedSecurity must be true if jcifs.smb.lmCompatibility >= 3

then ...

• In the YADE start script (jade.sh, jade2dmz.sh) add the java parameter

  -Djcifs.smb.lmCompatibility=0
  

• Example for the current command line:

  "%JAVA_BIN%" %LOG4JPROP% -classpath "%CP%" com.sos.DataExchange.SOSDataExchangeEngineMain %*
  

• Example for the changed command line:

  "%JAVA_BIN%" %LOG4JPROP% -Djcifs.smb.lmCompatibility=0 -classpath "%CP%" com.sos.DataExchange.SOSDataExchangeEngineMain %*