[
https://issues.apache.org/jira/browse/CONNECTORS-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823745#comment-16823745
]
Karl Wright commented on CONNECTORS-1498:
-----------------------------------------
Some of these settings should not be changed from a specific value. Other
settings I could see changing on a per-connection basis.
jcifs-ng does give the ability to control settings per connection, unlike the
original jcifs. But I think that the ones that should be connection-based
would be only:
- jcifs.resolveOrder
- jcifs.smb.client.minVersion
- jcifs.smb.client.maxVersion
- jcifs.smb.client.ipcSigningEnforced
The first thing to do is verify that the ported code works properly though.
> 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)
