nasftp: rename fails when a mount path is set |
||||
Issue descriptionChrome Version: 63.0.3239.50 OS: Chrome OS 10032.39.0 What steps will reproduce the problem? (1) Use the Secure Shell app to mount an SFTP server and specify a mount path. (2) Create a directory on the remote server. (3) Attempt to rename this directory from "New Folder". What is the expected result? Directory should be renamed. What happens instead? An error is reported.
,
Nov 24 2017
The following revision refers to this bug: https://chromium.googlesource.com/apps/libapps/+/b73450642cdac98a0125825020c26a14a8a5cd3c commit b73450642cdac98a0125825020c26a14a8a5cd3c Author: Reilly Grant <reillyg@chromium.org> Date: Fri Nov 24 15:09:46 2017 nassh: Set base path for SFTP RENAME and SETSTAT packets For these packets the path was not being prefixed with the base mount path which meant that the server would report "no such file" when not using the default mount path and performing a rename. Bug: chromium:788285 Change-Id: I84d46a10597f66d61ec8ba684d6a0e545fcf50c2 Reviewed-on: https://chromium-review.googlesource.com/788730 Tested-by: Reilly Grant <reillyg@chromium.org> Reviewed-by: Mike Frysinger <vapier@chromium.org> [modify] https://crrev.com/b73450642cdac98a0125825020c26a14a8a5cd3c/nassh/js/nassh_sftp_client.js
,
Nov 24 2017
,
Jan 22 2018
,
Jan 23 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by vapier@chromium.org
, Nov 24 2017