commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "L (JIRA)" <>
Subject [jira] [Commented] (VFS-617) isReadable fails if unable to determine group identity
Date Wed, 05 Apr 2017 08:13:41 GMT


L commented on VFS-617:

The thing is: this operation would always fail, no matter where it is invoked, on move() or
on login, if exec channel is not allowed or id command is not present.

I actually was forced to patch commons-vfs locally. I have added a new SFTP configuration
option in class SftpFileSystemConfigBuilder, which I called hardcodedRWXPermissions. When
true, doIsExecutable/doIsReadable/doIsWriteable always return true. This way I avoid executing
"id". Instead I rely on jssh to report errors if the actual file operation fails. Works like
a charm.

> isReadable fails if unable to determine group identity
> ------------------------------------------------------
>                 Key: VFS-617
>                 URL:
>             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
> 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(
> 	at com.avenca.vfs.VFSUtils.main(
> 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(
> 	at org.apache.commons.vfs2.provider.sftp.SftpFileObject.getPermissions(
> 	at org.apache.commons.vfs2.provider.sftp.SftpFileObject.doIsReadable(
> 	at org.apache.commons.vfs2.provider.AbstractFileObject.isReadable(
> 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

This message was sent by Atlassian JIRA

View raw message