[ 
https://issues.apache.org/jira/browse/CONNECTORS-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823727#comment-16823727
 ] 

Tang Huan Song commented on CONNECTORS-1498:
--------------------------------------------

In addition to the changes required for the upgrade to utilize jcifs-ng over 
the current jcifs library, I'd like to also suggest allowing the user to tweak 
basic jcifs/jcifs-ng parameters in order to suit the target fileserver.

I'm unsure whether it's better to make it a connector-wide setting (and have it 
adjustable via ManifoldCF's properties.xml) or have it modifiable 
per-connection, but at the moment I have the former in mind.

Perhaps implementation could go like the following, placed within a static 
block in the SharedDriveConnector class.



{code:java}
    System.setProperty("jcifs.smb.client.soTimeout", 
ManifoldCF.getStringProperty("jcifs.smb.client.soTimeout", "..."));
{code}


with the following settings and their suggested defaults:

* jcifs.smb.client.soTimeout: 150000
* jcifs.smb.client.responseTimeout: 120000
* jcifs.resolveOrder: DNS
* jcifs.smb.client.listCount: 20
* jcifs.smb.client.dfs.strictView: true
* jcifs.traceResources: true
* jcifs.smb.client.minVersion: SMB1
* jcifs.smb.client.maxVersion: SMB210
* jcifs.traceResources: true
* jcifs.smb.client.ipcSigningEnforced: true

> Support SMBv2/v3 protocol for Windows Shares connector
> ------------------------------------------------------
>
>                 Key: CONNECTORS-1498
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1498
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: JCIFS connector
>         Environment: OS: CentOS 7.2
> ManifoldCF: 2.8.1
>            Reporter: Hiroaki Takasu
>            Assignee: Karl Wright
>            Priority: Major
>             Fix For: ManifoldCF 2.10
>
>
> Windows Shares connector  (JCIFS connector) uses 
> [JCIFS|https://jcifs.samba.org/] library which supports only samba protocol 
> v1.
> But many file servers were disabled SMBv1 by vulnerability 
> [MS17-010|https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2017/ms17-010],
>  so we can not use Windows Shares connector.
> I hope that ManifoldCF support SMBv2/v3 with other CIFS library (e.g. 
> [smbj|https://github.com/hierynomus/smbj])



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to