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

Vineet Tyagi commented on VFS-617:
----------------------------------

[~gwarawate] Its an issue as they have changed a lot (after 2.0) the way it  
connects to sftp server.  In 2.0 isReadable and isWritable returns true and no 
check for the group ids etc. The solution as of now it to rollback to 2.0

 

Thanks

Vineet

> isReadable fails if unable to determine group identity
> ------------------------------------------------------
>
>                 Key: VFS-617
>                 URL: https://issues.apache.org/jira/browse/VFS-617
>             Project: Commons VFS
>          Issue Type: Bug
>    Affects Versions: 2.1
>         Environment: Windows 7 Java 7. Failure occured connecting via SFTP to 
> a Synology box running DSM 6.
>            Reporter: Tim Nickels
>            Priority: Major
>
> The doIsReadable method of SftpFileObject throws an exception if the system 
> cannot identify group/owner permissions....... 
> Exception in thread "main" org.apache.commons.vfs2.FileSystemException: Could 
> not determine if file "sftp://myURI"; is readable.
>       at 
> org.apache.commons.vfs2.provider.AbstractFileObject.isReadable(AbstractFileObject.java:1761)
>       at com.avenca.vfs.VFSUtils.main(VFSUtils.java:41)
> Caused by: com.jcraft.jsch.JSchException: Could not get the groups id of the 
> current user (error code: 1)
>       at 
> org.apache.commons.vfs2.provider.sftp.SftpFileSystem.getGroupsIds(SftpFileSystem.java:263)
>       at 
> org.apache.commons.vfs2.provider.sftp.SftpFileObject.getPermissions(SftpFileObject.java:317)
>       at 
> org.apache.commons.vfs2.provider.sftp.SftpFileObject.doIsReadable(SftpFileObject.java:335)
>       at 
> org.apache.commons.vfs2.provider.AbstractFileObject.isReadable(AbstractFileObject.java:1757)
> The problem is the method is using 
> return getPermissions(true).isReadable()
> The folder *is* readable without these permissions, and so should be set to
> return getPermissions(false).isReadable()
> Which correctly allows the system to identify a readable folder without 
> adding unnecessary restrictions.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to