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

Lukas Waldmann commented on SSHD-730:
-------------------------------------

Imagine dir tree like this:
/dir1/dir2/file
/dir1/dir3/link

if "link" is ../dir2/file than normalizePath in sendLink function returns: 
dir2/file
But your current directory is dir3 and if you want to process this link you 
don't have any knowledge where dir2 is located because normalizePath doesn't 
return absolute path neither keeps relative location of dir2 to dir3

I don't know why normalizePath call was introduced but it seems it screws 
handling of relative paths in links

> Relative symbolic links with .. is not resolved properly by sftp readLink
> -------------------------------------------------------------------------
>
>                 Key: SSHD-730
>                 URL: https://issues.apache.org/jira/browse/SSHD-730
>             Project: MINA SSHD
>          Issue Type: Bug
>    Affects Versions: 1.1.0, 1.2.0, 1.3.0
>            Reporter: Lukas Waldmann
>            Assignee: Goldstein Lyor
>            Priority: Minor
>
> Using sftp to resolve symbolic links doesn't return proper resolution in case 
> symbolic link contains ..
> Since version 1.1 the sendLink function of SftpSubsystem uses
> normalizedPath = SelectorUtils.normalizePath(unixPath, "/");
> to normalize path
> This function however return invalid path in case link contains ".."
> So for example if link is "../test/file" than normalizePath returns 
> "test/file" which is invalid because in can not be resolved properly in the 
> context of the current directory which symbolic link is referring to.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to