[jira] [Commented] (VFS-635) can't access SMBv2
[
https://issues.apache.org/jira/browse/VFS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144614#comment-16144614
]
Cody Swanson commented on VFS-635:
--
OK, I have a fork on GitHub that implements the smbj provider, but I am having
some trouble with the implementation absolute URIs in the SMB2FileProvider
class. I will keep working on this, but I appreciate any pointers or
suggestions!
> can't access SMBv2
> --
>
> Key: VFS-635
> URL: https://issues.apache.org/jira/browse/VFS-635
> Project: Commons VFS
> Issue Type: Wish
>Affects Versions: 2.0, 2.1
>Reporter: Michael
>
> After Disabling SMBV1 in windows I can't access into the filesystem.
> This code works when SMB1 is enabled, but sops to work once disabled.
> {code}
> @Test
> public void testConnection() throws FileSystemException {
> String login = "admin";
> String password = "password";
> String domain = "";
> String folder = "//10.0.0.0/smb";
> folder = folder.replaceAll("", "/");
> StringBuilder builder = new
> StringBuilder(128).append("smb").append(':').append(folder);
> String fileURI = builder.toString();
> FileSystemOptions fsOptions = null;
> StaticUserAuthenticator auth = new
> StaticUserAuthenticator(domain, login, password);
> fsOptions = new FileSystemOptions();
>
> DefaultFileSystemConfigBuilder.getInstance().setUserAuthenticator(fsOptions,
> auth);
> FileSystemManager manager = VFS.getManager();
> FileSystemManager fileSystemManager = manager;
> FileObject fileObject = fileSystemManager.resolveFile(fileURI,
> fsOptions);
> boolean result = fileObject.isReadable();
> System.out.println(fileURI +" " + result);
> }
> {code}
> this is how I disabled smb v1
> Set-ItemProperty -Path
> "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB1 -Type
> DWORD -Value 0 -Force
> How I enabled SMBV2
> Set-ItemProperty -Path
> "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB2 -Type
> DWORD -Value 1 -Force
> https://support.microsoft.com/en-us/help/2696547/how-to-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and-windows-server
> [TRACE]
> {code}
> org.apache.commons.vfs2.FileSystemException: Could not determine if file
> "smb://10.0.0.0/smb/" is readable.
> at
> org.apache.commons.vfs2.provider.AbstractFileObject.isReadable(AbstractFileObject.java:1761)
> at com.pa.util.files.FileUtilsTest.testConnection(FileUtilsTest.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:678)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
> Caused by: org.apache.commons.vfs2.FileSystemException:
[jira] [Comment Edited] (VFS-635) can't access SMBv2
[
https://issues.apache.org/jira/browse/VFS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144614#comment-16144614
]
Cody Swanson edited comment on VFS-635 at 8/29/17 12:54 AM:
OK, I have a fork on GitHub that implements the smbj provider, but I am having
some trouble with the implementation absolute URIs in the SMB2FileProvider
class. I will keep working on this, but I appreciate any pointers or
suggestions!
https://github.com/codyswanson4/commons-vfs/commit/664d654f2c85ed50737e1c04b1e483ace3827ef2
was (Author: codyswanson4):
OK, I have a fork on GitHub that implements the smbj provider, but I am having
some trouble with the implementation absolute URIs in the SMB2FileProvider
class. I will keep working on this, but I appreciate any pointers or
suggestions!
> can't access SMBv2
> --
>
> Key: VFS-635
> URL: https://issues.apache.org/jira/browse/VFS-635
> Project: Commons VFS
> Issue Type: Wish
>Affects Versions: 2.0, 2.1
>Reporter: Michael
>
> After Disabling SMBV1 in windows I can't access into the filesystem.
> This code works when SMB1 is enabled, but sops to work once disabled.
> {code}
> @Test
> public void testConnection() throws FileSystemException {
> String login = "admin";
> String password = "password";
> String domain = "";
> String folder = "//10.0.0.0/smb";
> folder = folder.replaceAll("", "/");
> StringBuilder builder = new
> StringBuilder(128).append("smb").append(':').append(folder);
> String fileURI = builder.toString();
> FileSystemOptions fsOptions = null;
> StaticUserAuthenticator auth = new
> StaticUserAuthenticator(domain, login, password);
> fsOptions = new FileSystemOptions();
>
> DefaultFileSystemConfigBuilder.getInstance().setUserAuthenticator(fsOptions,
> auth);
> FileSystemManager manager = VFS.getManager();
> FileSystemManager fileSystemManager = manager;
> FileObject fileObject = fileSystemManager.resolveFile(fileURI,
> fsOptions);
> boolean result = fileObject.isReadable();
> System.out.println(fileURI +" " + result);
> }
> {code}
> this is how I disabled smb v1
> Set-ItemProperty -Path
> "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB1 -Type
> DWORD -Value 0 -Force
> How I enabled SMBV2
> Set-ItemProperty -Path
> "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB2 -Type
> DWORD -Value 1 -Force
> https://support.microsoft.com/en-us/help/2696547/how-to-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and-windows-server
> [TRACE]
> {code}
> org.apache.commons.vfs2.FileSystemException: Could not determine if file
> "smb://10.0.0.0/smb/" is readable.
> at
> org.apache.commons.vfs2.provider.AbstractFileObject.isReadable(AbstractFileObject.java:1761)
> at com.pa.util.files.FileUtilsTest.testConnection(FileUtilsTest.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at
>
[jira] [Updated] (BCEL-276) LocalVariableTypeTable is not updated.
[ https://issues.apache.org/jira/browse/BCEL-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Roberts updated BCEL-276: -- Attachment: (was: MethodGen.mark.diff) > LocalVariableTypeTable is not updated. > --- > > Key: BCEL-276 > URL: https://issues.apache.org/jira/browse/BCEL-276 > Project: Commons BCEL > Issue Type: Bug >Affects Versions: 6.0 >Reporter: Sam Yoon >Assignee: Benedikt Ritter > Labels: github > Fix For: 6.1 > > Attachments: LocalVariableGen.mark.diff, LocalVariable.mark.diff, > LocalVariableTypeTableTest.java, MethodGen.mark.diff2, > SimpleClassHasMethodIncludeGenericArgument.java > > > If a method for BCI have at least one generic type of argument JVM throw > java.lang.ClassFormatError due to not updated LocalVariableTable. > I know there is workaround as call removeLocalVariables method. > But I think it's better that BCEL can stay proper LocalVariableTable. > I'm also pull test case can reproduce error. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (BCEL-276) LocalVariableTypeTable is not updated.
[ https://issues.apache.org/jira/browse/BCEL-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Roberts updated BCEL-276: -- Attachment: (was: MethodGen.diff) > LocalVariableTypeTable is not updated. > --- > > Key: BCEL-276 > URL: https://issues.apache.org/jira/browse/BCEL-276 > Project: Commons BCEL > Issue Type: Bug >Affects Versions: 6.0 >Reporter: Sam Yoon >Assignee: Benedikt Ritter > Labels: github > Fix For: 6.1 > > Attachments: LocalVariableGen.mark.diff, LocalVariable.mark.diff, > LocalVariableTypeTableTest.java, MethodGen.mark.diff, MethodGen.mark.diff2, > SimpleClassHasMethodIncludeGenericArgument.java > > > If a method for BCI have at least one generic type of argument JVM throw > java.lang.ClassFormatError due to not updated LocalVariableTable. > I know there is workaround as call removeLocalVariables method. > But I think it's better that BCEL can stay proper LocalVariableTable. > I'm also pull test case can reproduce error. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (BCEL-276) LocalVariableTypeTable is not updated.
[ https://issues.apache.org/jira/browse/BCEL-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Roberts updated BCEL-276: -- Attachment: MethodGen.mark.diff2 > LocalVariableTypeTable is not updated. > --- > > Key: BCEL-276 > URL: https://issues.apache.org/jira/browse/BCEL-276 > Project: Commons BCEL > Issue Type: Bug >Affects Versions: 6.0 >Reporter: Sam Yoon >Assignee: Benedikt Ritter > Labels: github > Fix For: 6.1 > > Attachments: LocalVariableGen.mark.diff, LocalVariable.mark.diff, > LocalVariableTypeTableTest.java, MethodGen.mark.diff, MethodGen.mark.diff2, > SimpleClassHasMethodIncludeGenericArgument.java > > > If a method for BCI have at least one generic type of argument JVM throw > java.lang.ClassFormatError due to not updated LocalVariableTable. > I know there is workaround as call removeLocalVariables method. > But I think it's better that BCEL can stay proper LocalVariableTable. > I'm also pull test case can reproduce error. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (BCEL-276) LocalVariableTypeTable is not updated.
[ https://issues.apache.org/jira/browse/BCEL-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144471#comment-16144471 ] Mark Roberts commented on BCEL-276: --- This does not appear to be corrected in the current sources. I have updated the patch for MethodGen to sync with changes made from my last upload. It is now called MethodGen.mark.diff2. > LocalVariableTypeTable is not updated. > --- > > Key: BCEL-276 > URL: https://issues.apache.org/jira/browse/BCEL-276 > Project: Commons BCEL > Issue Type: Bug >Affects Versions: 6.0 >Reporter: Sam Yoon >Assignee: Benedikt Ritter > Labels: github > Fix For: 6.1 > > Attachments: LocalVariableGen.mark.diff, LocalVariable.mark.diff, > LocalVariableTypeTableTest.java, MethodGen.diff, MethodGen.mark.diff, > SimpleClassHasMethodIncludeGenericArgument.java > > > If a method for BCI have at least one generic type of argument JVM throw > java.lang.ClassFormatError due to not updated LocalVariableTable. > I know there is workaround as call removeLocalVariables method. > But I think it's better that BCEL can stay proper LocalVariableTable. > I'm also pull test case can reproduce error. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NET-642) using execPROT on FTPSClients with Proxy Settings removes Proxy Settings
[ https://issues.apache.org/jira/browse/NET-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143544#comment-16143544 ] Johannes Frank commented on NET-642: Any thoughts on my PR? > using execPROT on FTPSClients with Proxy Settings removes Proxy Settings > > > Key: NET-642 > URL: https://issues.apache.org/jira/browse/NET-642 > Project: Commons Net > Issue Type: Bug > Components: FTP >Affects Versions: 3.6 > Environment: Java 1.8.0_112 > Linux 64bit >Reporter: Johannes Frank >Priority: Critical > > In Reference to https://issues.apache.org/jira/browse/NET-578 > I'm trying to establish an FTPS Connection via a HTTP Proxy. The Control > Connection is properly established, however the Moment I do execPROT the > Proxy settings are resetted by call to setSocketFactory(new > FTPSSocketFactory(context)); in FTPSClient.java:534. > This causes FTPSClients with a call to execPROT to actually ignore the proxy > settings and attempt to contact the FTPS Server directly for data connections. > Since we are required to use PROT P this is currently blocking our feature > for FTPS Connections via HTTP proxy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
