[Cyberduck-trac] [Cyberduck] #9813: Edit command changes permission of file, even if only reading the file

[Cyberduck]

#9813: Edit command changes permission of file, even if only reading the file
------------------------+----------------------
 Reporter:  tempelmann  |         Owner:
     Type:  defect      |        Status:  new
 Priority:  high        |     Milestone:
Component:  core        |       Version:  5.2.2
 Severity:  normal      |    Resolution:
 Keywords:              |  Architecture:
 Platform:              |
------------------------+----------------------
Description changed by tempelmann:

Old description:

> I have the following dir:
>

> {{{
> drwxr-xr-x 2 edit www   4096 Jan 17 18:05 ./
> drwxr-xr-x 4 edit www   4096 Jan 16 00:42 ../
> -rw-rw-r-- 1 edit www  57569 Jan 17 18:09 news.log
> }}}
>
> Now, if I double click "news.log" in Cyberduck to view the file, its
> permissions immediately change to:
>
> {{{
> -rw-r--r-- 1 edit data  56894 Jan 17 18:05 news.log
> }}}
>
> I.e, it removes the groups write access. This is a severe bug, IMO. The
> permissions should not be changed for an existing file, ever, especially
> not if I only read it, not modify it.
>
> If I do the same with Cyberduck 4.7.2, the permissions remain unchanged,
> as expected. That should prove it's not a problem with my setup but with
> Cyberduck.
>
> Both versions have the same prefs, including the option "change
> permissions" for downloads (644). But that should only affect the file
> downloaded to my computer, not the file on the server, right?
>

> Access is via SFTP, if that matters.
>
> I've attached the prefs file, cleaned up a little (removing the NS...,
> bookmarks and session entries)

New description:

 I have the following dir:


 {{{
 drwxr-xr-x 2 edit www   4096 Jan 17 18:05 ./
 drwxr-xr-x 4 edit www   4096 Jan 16 00:42 ../
 -rw-rw-r-- 1 edit www  57569 Jan 17 18:09 news.log
 }}}

 Now, if I double click "news.log" in Cyberduck to view the file, its
 permissions immediately change to:

 {{{
 -rw-r--r-- 1 edit www  56894 Jan 17 18:05 news.log
 }}}

 I.e, it removes the groups write access. This is a severe bug, IMO. The
 permissions should not be changed for an existing file, ever, especially
 not if I only read it, not modify it.

 If I do the same with Cyberduck 4.7.2, the permissions remain unchanged,
 as expected. That should prove it's not a problem with my setup but with
 Cyberduck.

 Both versions have the same prefs, including the option "change
 permissions" for downloads (644). But that should only affect the file
 downloaded to my computer, not the file on the server, right?


 Access is via SFTP, if that matters.

 I've attached the prefs file, cleaned up a little (removing the NS...,
 bookmarks and session entries)

--

--
Ticket URL: <https://trac.cyberduck.io/ticket/9813#comment:2>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows