Opened 10 years ago
Closed 10 years ago
#10000 closed Bug report (fixed)
Permissions wrong on transfer
Reported by: | Michael E. | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | FileZilla Client |
Keywords: | Cc: | ||
Component version: | Operating system type: | OS X | |
Operating system version: | OS X 10.10.1 |
Description
I use public key authentication for sftp. When files are transferred with FileZilla Client 3.10.0 file permission are not being set properly. They are being set to 000. Previous versions handled the permissions correctly.
FileZilla Client
Version: 3.10.0
Build information:
Compiled for: i386-apple-darwin13.2.0
Compiled on: i386-apple-darwin13.2.0
Build date: 2015-01-07
Compiled with: Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn)
Compiler flags: -g -O2 -Wall -g -fexceptions -std=gnu++11
Linked against:
wxWidgets: 3.0.3
GnuTLS: 3.2.20
SQLite: 3.8.6
Operating system:
Name: Mac OS X (Darwin 14.0.0 x86_64)
Version: 10.10
Attachments (1)
Change History (12)
by , 10 years ago
Attachment: | FileZilla_permission_issue.png added |
---|
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Confirmed on (probably) v3.10.0 and v3.10.0.1 when uploading with private key to a chrooted/jailed SFTP server. Permissions are set to 000. Uploading with a different SFTP client works properly, so it's not a remote system umask problem. The remote configuration of the SFTP server:
Port 22 Protocol 2 HostKey /etc/ssh/ssh_host_rsa_key HostKey /etc/ssh/ssh_host_dsa_key HostKey /etc/ssh/ssh_host_ecdsa_key UsePrivilegeSeparation yes KeyRegenerationInterval 3600 ServerKeyBits 768 SyslogFacility AUTH LogLevel INFO LoginGraceTime 120 PermitRootLogin yes StrictModes yes RSAAuthentication yes PubkeyAuthentication yes IgnoreRhosts yes RhostsRSAAuthentication no HostbasedAuthentication no PermitEmptyPasswords no ChallengeResponseAuthentication no X11Forwarding yes X11DisplayOffset 10 PrintMotd no PrintLastLog yes TCPKeepAlive yes AcceptEnv LANG LC_* Subsystem sftp internal-sftp UsePAM yes Match group sftponly ChrootDirectory /home/%u/external X11Forwarding no AllowTcpForwarding no ForceCommand internal-sftp
Moving back to an older version of Filezilla (v3.9.0.6) solves the problem.
Regards,
comment:3 by , 10 years ago
Operating system version: | MacOS 10.10.1 → MacOS 10.9.5 |
---|
Also experiencing this, using client 3.10.0 with Mac OS 10.9.5
comment:4 by , 10 years ago
Status: | new → moreinfo |
---|
SFTP support in FileZilla is based upon PuTTY's psftp.
Do you also experience this issue if you transfer files using the latest psftp development snapshot from PuTTY?
comment:5 by , 10 years ago
Status: | moreinfo → new |
---|
Both the original reporter and I reported this bug on Mac OS – I don't believe PuTTY is available for Mac. If I'm missing a trick please let me know and I'll follow any guidance I'm given! Otherwise I could perhaps see if the bug can be replicated on Windows?
comment:6 by , 10 years ago
I am on a Mac and am unable to find a PuTTY version.
Where previous builds of FileZilla be download from?
comment:7 by , 10 years ago
Operating system version: | MacOS 10.9.5 → OS X 10.10.1 |
---|
I have the same issue. When uploading new files, they get permission 000
running Filezilla 3.10.0.1 on OS X 10.10.1
comment:8 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
This will be fixed in the next version of FileZilla which will be out in a few days at most.
comment:9 by , 10 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Can't confirm. Issue still exists with build 3.10.0.2 on OS X 10.10.1 !!
Permissions 000 when connected via public key to cents 6.5 x64
comment:10 by , 10 years ago
The customer who initially reported the problem to me has confirmed that the problem has gone away with the latest FileZilla release. I can't test it myself, as I don't have a Mac. I assume he's running 3.10.0.2, but I can't be sure other than "the latest version".
comment:11 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Make sure the source file permissions are set correctly prior to the transfer.
Replying to essermi: I'm having this problem too!