[jira] [Commented] (CONNECTORS-1498) Support SMBv2/v3 protocol for Windows Shares connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16821570#comment-16821570 ] Karl Wright commented on CONNECTORS-1498: - Ok, I got past the build problems and made (what I think) are the necessary changes. Please check out https://svn.apache.org/repos/asf/manifoldcf/branches/CONNECTORS-1498 and try it. Thanks! > 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)
[jira] [Commented] (CONNECTORS-1498) Support SMBv2/v3 protocol for Windows Shares connector
[
https://issues.apache.org/jira/browse/CONNECTORS-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16821562#comment-16821562
]
Karl Wright commented on CONNECTORS-1498:
-
[~hhoechtl], I just tried this. The compilation errors are the following:
{code}
compile-connector:
[javac] C:\wip\mcf\trunk\dist\connector-build.xml:594: warning:
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to
false for repeatable builds
[javac] Compiling 6 source files to
C:\wip\mcf\trunk\connectors\jcifs\build\connector\classes
[javac]
C:\wip\mcf\trunk\connectors\jcifs\connector\src\main\java\org\apache\manifoldcf\crawler\connectors\sharedrive\SharedDriveConnector.java:20:
warning: [deprecation] NtlmPasswordAuthentication in jcifs.smb has been
deprecated
[javac] import jcifs.smb.NtlmPasswordAuthentication;
[javac] ^
[javac]
C:\wip\mcf\trunk\connectors\jcifs\connector\src\main\java\org\apache\manifoldcf\crawler\connectors\sharedrive\SharedDriveHelpers.java:35:
warning: [deprecation] NtlmPasswordAuthentication in jcifs.smb has been
deprecated
[javac] import jcifs.smb.NtlmPasswordAuthentication;
[javac] ^
[javac]
C:\wip\mcf\trunk\connectors\jcifs\connector\src\main\java\org\apache\manifoldcf\crawler\connectors\sharedrive\SharedDriveConnector.java:19:
error: cannot find symbol
[javac] import jcifs.smb.ACE;
[javac] ^
[javac] symbol: class ACE
[javac] location: package jcifs.smb
[javac]
C:\wip\mcf\trunk\connectors\jcifs\connector\src\main\java\org\apache\manifoldcf\crawler\connectors\sharedrive\SharedDriveConnector.java:20:
warning: [deprecation] NtlmPasswordAuthentication in jcifs.smb has been
deprecated
[javac] import jcifs.smb.NtlmPasswordAuthentication;
[javac] ^
[javac]
C:\wip\mcf\trunk\connectors\jcifs\connector\src\main\java\org\apache\manifoldcf\crawler\connectors\sharedrive\SharedDriveConnector.java:1246:
error: cannot find symbol
[javac] protected void convertACEs(List allowList, List
denyList, ACE[] aces)
[javac]
^
[javac] symbol: class ACE
[javac] location: class SharedDriveConnector
[javac]
C:\wip\mcf\trunk\connectors\jcifs\connector\src\main\java\org\apache\manifoldcf\crawler\connectors\sharedrive\SharedDriveConnector.java:2404:
error: cannot find symbol
[javac] protected static ACE[] getFileSecurity(SmbFile file, boolean
useSIDs)
[javac]^
[javac] symbol: class ACE
[javac] location: class SharedDriveConnector
[javac]
C:\wip\mcf\trunk\connectors\jcifs\connector\src\main\java\org\apache\manifoldcf\crawler\connectors\sharedrive\SharedDriveConnector.java:2442:
error: cannot find symbol
[javac] protected static ACE[] getFileShareSecurity(SmbFile file, boolean
useSIDs)
[javac]^
[javac] symbol: class ACE
[javac] location: class SharedDriveConnector
[javac]
C:\wip\mcf\trunk\connectors\jcifs\connector\src\main\java\org\apache\manifoldcf\crawler\connectors\sharedrive\SharedDriveHelpers.java:34:
error: cannot find symbol
[javac] import jcifs.smb.ACE;
[javac] ^
[javac] symbol: class ACE
[javac] location: package jcifs.smb
[javac]
C:\wip\mcf\trunk\connectors\jcifs\connector\src\main\java\org\apache\manifoldcf\crawler\connectors\sharedrive\SharedDriveHelpers.java:35:
warning: [deprecation] NtlmPasswordAuthentication in jcifs.smb has been
deprecated
[javac] import jcifs.smb.NtlmPasswordAuthentication;
[javac] ^
[javac] 5 errors
[javac] 4 warnings
{code}
The thing that stops it from compiling is that there is no longer a class
jcifs.smb.ACE. This is an access-control list element. It's obviously
critical to the functioning of ManifoldCF to have that.
Can you research what happened to this in jcifs-ng? Did they just rename it,
or did they completely remove it?
> 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
[jira] [Commented] (CONNECTORS-1498) Support SMBv2/v3 protocol for Windows Shares connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16821122#comment-16821122 ] Karl Wright commented on CONNECTORS-1498: - [~hhoechtl], this looks like a reimplementation of JCIFS which in theory should support the same original JCIFS API. It is LGPL, which is consistent with the original JCIFS, so I believe it includes much of the original code. It might well work by just downloading the jar and treating it just like the original JCIFS. Have you tried this? > 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)
[jira] [Commented] (CONNECTORS-1498) Support SMBv2/v3 protocol for Windows Shares connector
[
https://issues.apache.org/jira/browse/CONNECTORS-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16821090#comment-16821090
]
Hans Höchtl commented on CONNECTORS-1498:
-
{quote}JCIFS has been in maintenance-mode-only for several years and although
what it does support works fine (SMB1, NTLMv2, midlc, MSRPC and various utility
classes), jCIFS does not support the newer SMB2/3 variants of the SMB protocol
{quote}
There's a new library that would support SMB v2/v3 but somebody would need to
change the connectors implementation.
[https://github.com/AgNO3/jcifs-ng]
> 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)
[jira] [Commented] (CONNECTORS-1599) response code 401 still gets deleted with the setting "keep unreachable documents"
[ https://issues.apache.org/jira/browse/CONNECTORS-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16820875#comment-16820875 ] roel goovaerts commented on CONNECTORS-1599: Hi [~kwri...@metacarta.com] Is there some resource which specifies the different technical responses of manifold to different http codes? Regards, Roel > response code 401 still gets deleted with the setting "keep unreachable > documents" > -- > > Key: CONNECTORS-1599 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1599 > Project: ManifoldCF > Issue Type: Bug > Components: Web connector >Affects Versions: ManifoldCF 2.12 >Reporter: roel goovaerts >Assignee: Karl Wright >Priority: Major > Fix For: ManifoldCF 2.13 > > > Even with the "Hop count mode" set to "keep unreachable documents, 'for now' > || forever" manifold deletes documents for which it receives a 401 response > code. > The documentation does not specify such a distinction as described above. Is > there some information/configuration that I'm missing? Is there a reasoning > behind the guaranteed deletion of a 401? > Ideally, for our use-case, we would want to remove all documents that return > 404, but keep everything which is due the server not responding or the > crawler being unauthenticated. > Is there a way to configure this in a more granular fashion? > Regards, > roel -- This message was sent by Atlassian JIRA (v7.6.3#76005)
