Custom Query (8170 matches)
Results (1801 - 1900 of 8170)
Ticket | Summary | Owner | Type | Priority | Component | Resolution | |
---|---|---|---|---|---|---|---|
#129 | bad local directory listing | Feature request | low | FileZilla Server | |||
Description |
Running 1.9.8 beta 6 on win98. Every item in the current folder is repeated at least 50 times - folders and files. |
||||||
#173 | rename to a name of an existing file | Bug report | normal | FileZilla Server | fixed | ||
Description |
I wanted to rename a filename on ftp server. Unfortunately, the filename I rename to is the same as an existing file! Finally, the existing file is replaced. Is this a bug? Thanks a lot |
||||||
#606 | Server: PORT does not accept IPs with leading zeros | Bug report | normal | FileZilla Server | fixed | ||
Description |
The FileZilla server can not open the data port when the port command looks like: PORT 192,168,160,010,80,51 Seems the leading zero in the 010 bothers him as changing the IP to 100 worked well. Just for the files: the client is a DEMAG injection moulding machine with an NC4 controller running a EuroMap63 protocol via FTP. They have a very lousy FTP implementation and for now only Serv-U and FileZilla (accept the mentioned flaw) work with it... |
||||||
#805 | Server is unable to transfer open files | Bug report | normal | FileZilla Server | fixed | ||
Description |
When you try to get a file that is open but not exclusive (it is still possible to do a copy on the local filesystem for example), FileZilla Server can't open it and a transfer error is reported. It would be nice if the server was able to transfer these files. I need this specifically for transferring open logfiles. These logfiles are created with the following code: CStdioFile::Open(filename,CFile::modeCreate | CFile::modeNoTruncate | CFile::modeWrite | CFile::shareDenyNone | CFile::typeText , &ex) I don't know if the server can't open these files by design or if it is a bug. Thanks! |
||||||
#810 | FileZilla Server | Bug report | normal | FileZilla Server | outdated | ||
Description |
This IS listed under older bugs, but was listed as a PROBLEM CAN NOT BE DUPLICATED. Just installed the latest version of FileZilla Server 0.9.4e. Server is behind a simple Netgear MR314 Port NAT device. Setup the Listening port to a valid port. Setup the Passive Mode with proper external address, and set the Passive ports to an allowed range. Connected from the outside world. All processes operate just great, upload, download, new dir, del etc... However, When I connect, I see 2 user sessions established for just one connection. Both have the same user account listed on them. I disconnect. One session drops, but the other remains active (at least it shows it is active in the active user list). Connect again... now I have 3 sessions with only one connection. Disconnect again. I still have 2 open sessions. When tested the same way from INSIDE the NAT device (on the LAN side), I see the correct 1 session established, and when I disconnect, that 1 session is torn down properly as well. Great product! If there is anything I can send to demonstrate this issue, please let me know! |
||||||
#813 | Filezilla server problems with assymmetrical links on win2k | Bug report | normal | FileZilla Server | outdated | ||
Description |
Filezilla server should be modified to do setsocketopt() for send and receive buffers so that assymmetrical links are handled better. ie
SO_SNDBUF, (char *) &window_size, sizeof (window_size));
SO_RCVBUF, (char *) &window_size, sizeof (window_size)); should be done before bind() |
||||||
#814 | Is this possible?? | Bug report | normal | FileZilla Server | |||
Description |
Hi, We are using FileZilla Server 0.9.3 for some testing in a lab environment. We have a second site that is FTP'ing files to the FileZilla server and once complete the client software (non-filezilla s/w) move the files to a done folder. We have encountered a situation where the client software reports that files have been sent but the filezilla server shows the files received roughly an hour later. Is this possible on the server side or would it appear to be a problem at the client side. I have attached a copy of the log file for a 3 hour period. The user name in question is "d_dsour_nc04". If you search the log file, d_dsour_nc04 logs in at 10:35:18 and dumps a file off, and then the next time that d_dsour_nc04 appears in the log is not until 11:35:36. The client machine shows that file where sent during this 1 hour period. Tell me we are not going crazy... Thanks, Stew |
||||||
#820 | FileZilla Server incredibly slow | Bug report | normal | FileZilla Server | |||
Description |
FileZilla Server 0.9.5 is incredibly slow. I was running it for and FTP server, but have since swapped it out for WARFTPd 1.82.0.10 because of the following performance numbers (notice that FileZilla is almost 3 times slower than WARFTPd, and Microsoft FTP is only about 1 sec slower than WARFTPd): FileZilla Server 0.9.5: ftp> get catalog.pdf 200 Port command successful 150 Opening data channel for file transfer. 226 Transfer OK ftp: 42509572 bytes received in 18.24Seconds 2330.95Kbytes/sec. Microsoft FTP Server 5.1 (XP): ftp> get catalog.pdf 200 PORT command successful. 150 Opening BINARY mode data connection for catalog.pdf(42509572 bytes). 226 Transfer complete. ftp: 42509572 bytes received in 8.14Seconds 5221.02Kbytes/sec. WARFTPd 1.82.00-RC10: ftp> get catalog.pdf 200 PORT command successful. 150 Opening BINARY mode data connection for catalog.pdf (42509572 bytes). 226 Transfer complete. 42509572 bytes in 7.00 sec. (5930.465 Kb/s) ftp: 42509572 bytes received in 6.99Seconds 6080.61Kbytes/sec. My platform is: Intel Pentium III 933 512 MB RAM Microsoft Windows XP SP2 |
||||||
#842 | Filezilla Server 0.9.6 - Admin Interface can't connect | Bug report | normal | FileZilla Server | outdated | ||
Description |
Installed Filezilla server 0.9.6 (as a service) on top of 0.9.5 and the admin interface is not able to connect (using default settings everywhere). |
||||||
#843 | Password prompt for anonymous user is misleading | Bug report | normal | FileZilla Server | wontfix | ||
Description |
I set up an anonymous user which does not require a password to login. The FileZilla FTP server still tells the anonymous user that a password is required, but you can just hit enter and you're in. I think that if no password is required, then the server should allow the user in without prompting for a password that isn't used. In addition, the user "anonymous" can be treated specially with a preference that asks the user to enter their email address in place of the password. Other FTP servers do this. |
||||||
#850 | Login Server Bug | Bug report | normal | FileZilla Server | outdated | ||
Description |
when the ftp client is inputting the account name for "user authentication", the connection suddenly hangup,and the server (CPU) usage rate increased to 100% at the same time. |
||||||
#857 | FileZilla Server service restart loses aliases | Bug report | normal | FileZilla Server | worksforme | ||
Description |
Hi, I have FileZilla Server 0.9.6a beta running as a service with Administrator rights. FileZilla Server forgets the alias settings on restart. Also on /reload-config using command line. However they remain in the FileZilla Server.xml file and can be copied and pasted back into the interface whereupon everything works. thank you so much for this program, please fix this (if I am right to say this is a bug) then I can use a front end application server to edit the xml file and restart FileZilla server, giving me instant remote control of the creation of accounts and alteration of IP address scope for more secure sessions etc.... |
||||||
#880 | Server installer: wrong description admin interface componen | Bug report | normal | FileZilla Server | fixed | ||
Description |
Small nit: when running the installer of Filezilla Server v0.9.8 the description of the 'Administration Interface' component is the same as the one for the 'Source Code' component ('Choose Components' screen). |
||||||
#886 | wilcard file listing on aliased directories | Bug report | normal | FileZilla Server | |||
Description |
wildcard file listing does not appear to work correctly fir aliased directories. As an example, a directory 'common' is aliased as a link in the user's home directory :- <><> 230 Logged on ftp> dir 200 Port command successful 150 Opening data channel for directory list. drwxr-xr-x 1 ftp ftp 0 May 23 13:41 common -rw-r--r-- 1 ftp ftp 335 May 23 13:41 file1.txt -rw-r--r-- 1 ftp ftp 382 May 23 13:41 file2.txt -rw-r--r-- 1 ftp ftp 429 May 23 13:41 file3.txt 226 Transfer OK ftp: 237 bytes received in 0.01Seconds 23.70Kbytes/sec. ftp> dir f* 200 Port command successful 150 Opening data channel for directory list. -rw-r--r-- 1 ftp ftp 335 May 23 13:41 file1.txt -rw-r--r-- 1 ftp ftp 382 May 23 13:41 file2.txt -rw-r--r-- 1 ftp ftp 429 May 23 13:41 file3.txt 226 Transfer OK ftp: 180 bytes received in 0.01Seconds 18.00Kbytes/sec. ftp> cd common 250 CWD successful. "/common" is current directory. ftp> dir 200 Port command successful 150 Opening data channel for directory list. -r--r--r-- 1 ftp ftp 337 May 23 13:41 file1.txt -r--r--r-- 1 ftp ftp 384 May 23 13:41 file2.txt -r--r--r-- 1 ftp ftp 431 May 23 13:41 file3.txt 226 Transfer OK ftp: 180 bytes received in 0.01Seconds 18.00Kbytes/sec. ftp> dir f* 200 Port command successful 150 Opening data channel for directory list. 226 Transfer OK ftp> quit 221 Goodbye <><> Trying to do a "dir f*" in the user's home directory works ok but it fails in the "common" directory, which has been aliased. server version 0.98a server is accessible via the internet - I can provide logon credentials for you to verify setup if needed. |
||||||
#889 | [FZ Server] LIST command failure when in alias'd directory | Bug report | normal | FileZilla Server | |||
Description |
After connecting to FZS (from every non-gui client I've tried), and I change directory to an alias'd directory, when attempting to use the command "dir *.zip", no files are viewed. When doing the straight "dir", it retrieves all files and directories. If I'm in my home directory, it works fine. All flags are turned on for the directory that's aliased. Can't think of anything else that could be going wrong.
works fine (ruling out any permissions problems). Running Win2k, using FZS 0.9.8 beta. If you need to know, I was using the ftp client built in to AIX. I also attempted using MS's FTP client localling on the same server and got the same thing (ruling out any network problems). I went into debug mode and it states it's sending a LIST *.zip as expected, but the server isn't sending back anything. |
||||||
#893 | INVALID BUG! | Bug report | normal | FileZilla Server | |||
Description |
This happened to the FZ Server 0.9.8a. It seems like the secure server partially works. I can create secure connection(s) w/o any problem and everything works fine if both server and client are on the same machine. I believe it should work if the server and the client are on different machines of the same LAN (please read on). However, If the server is on the Internet (not behind NAT or anything) and the client is behind NAT, I could connect to the server but I would get a 425 cannot open data connection error. Here is what I found after some quick investigations: I could see 2 connections made by the server with port 20 and 21 (I couldn’t get the 990 port working); however, one of the connections was not correct. The wrong one was trying to connect to the internal IP of the client, which is not reachable from the Internet. To reproduce:
SSL/TLS settings
explicit SSL
connect to the server and use FTP over SSL (explicit encryption)
Please note: the client is behind a NAT and the server is on the Internet. THANK YOU VERY MUCH FOR CREATING SUCH GREAT FTP SERVER/CLIENT! |
||||||
#899 | Apparent invalid response to AUTH TLS command | Bug report | normal | FileZilla Server | |||
Description |
Several of us are having issues trying to run FTP/S from IBM's mainframe FTP client to FZS. The mainframe sends "AUTH TLS" to which FZS responds with what IBM says the RFC says is an invalid 334 response. The IBM z/OS mainframe client thus never achieves a log on. We are seeing similar behavior out of the gFTP client from Red Hat Linux. This sequence is described in the FZ Help forum from the thread at: From Thread: http://sourceforge.net/forum/forum.php?thread_id=1295591&forum_id=68109 To quote the relevant exchanges: By: krupa38 - mwarnecke FZS with AUTH TLS and z/OS FTP client 2005-06-03 07:45 I tried to connect to FZS 0.9.8 with IBM's z/OS FTP client and AUTH TLS. A IP packet trace shows that after sending the AUTH TLS command FZS sends back a "334 Using authentication type TLS" which in turn is answered by "QUIT" from the client immediately. Does the client miss the the optional ADAT= data ? Any help would be welcome. By: Dave Gibney - gibney RE: FZS with AUTH TLS and z/OS FTP client 2005-06-08 18:14 This is a response to this question on an IBM forum: You are getting a 334 response back. The IBM client is expecting the SSL server to send back a 234. When you send a AUTH TLS a 234 is the only response the IBM client will accept. I ran into this problem with a windows server. I opened a problem with IBM after reading RFC2228 when it appeared from the surface a 334 was a valid response. Here is IBM reply to my etr: RFC2228 is a generic security RFC. the TLS specific information can be found at URL below http://www.ietf.org/internet-drafts/draft-murray-auth-ftp-ssl-16.txt where it states... 5.2 Server wants a secured session The FTP protocol does not allow a server to directly dictate client behaviour, however the same effect can be achieved by refusing to accept certain FTP commands until the session is secured to an acceptable level to the server. in either case, the server response to an 'AUTH TLS' command which it will honour, is '234'. The '334' response as defined in RFC-2228 implies that an ADAT exchange will follow. This document does not use the ADAT command and so the '334' reply is incorrect. . let us know if that answer your question When we replace FZS with commercial FTP servers such as the GlobalScape Secure FTP Server, the IBM mainframe is able to successfully connect. Many corporate and contract users are going to have to interact with the IBM mainframe platform. Please consider resolving this issue. |
||||||
#900 | Security Defect on IP filter. | Bug report | normal | FileZilla Server | |||
Description |
When *.*.*.* is typed into the IP filters (any of them) to block all IP addresses (turn the server off effectively), the server sends a response when a connection attempt is made. Currently it sends the welcome message. This allows anyone sniffing for an FTP server to confirm there is indeed a server there. It should NOT send a response - ie. it should be in stealth mode. The result is that the server may then suffer a Denial of Service attack on that port. This causes a secondary error in that the FTP server tries to send the welcome message back to every connection attempt (which should not be allowed) and promptly kills the server. Not only that but us poor sods who have to pay for our data usage (or have traffic limits) then promptly get a large bill. |
||||||
#902 | Share in Filezilla | Bug report | normal | FileZilla Server | |||
Description |
There is a problem with sharing folders from diferent partisions (c:, D: ...) in filezilla. Only the home dir is available to browse in. |
||||||
#903 | Potential bug in sending files (+proposed fix) | Bug report | blocker | FileZilla Server | |||
Description |
There is a bug I've just fixed in the XBFileZilla version we use in XBoxMediaCenter that appears to still have the potential to be there in the latest CVS code of FileZilla. XBFileZilla that we use is based off FileZilla version 0.8.3 or thereabouts, so is reasonably old, however the code in question has not changed all that much. The interesting thing is that the bug itself only crops up on certain filesizes, and only on certain systems (network setups). For instance, I couldn't get it to reproduce on my system at all, yet the same executeable screwed up on several other systems. The bug is in TransferSocket.cpp, around line 518. There is a block of code that checks whether the number of bytes read from the ReadFile() call is 0, and if so, closes the file and stops the transfer (calling Close() etc.) The problem that occurs is that the buffer is filled at the previous call to CTransferSocket::OnSend(), yet is not fully emptied on that call (due to network traffic complications or whatever). Thus, the call to ReadFile() returns no data read, and so the code block closes the transfer, effectively terminating the transfer prematurely. No error is reported, so the user is unaware of the corrupted transfer, unless a CRC check etc. is issued later. The fix, ofcourse, is to check first for an empty buffer before calling Close(). In our local version of the code, I've changed:
m_pOwner->m_pOwner->PostThreadMessage(WM_FILEZILLA_THREADMSG, FTM_TRANSFERMSG, m_pOwner->m_userid);
to:
m_pOwner->m_pOwner->PostThreadMessage(WM_FILEZILLA_THREADMSG, FTM_TRANSFERMSG, m_pOwner->m_userid);
Let me know if I can be of more assistance, or if you have any idea of why it cropped up in the first place ;) Cheers, Jonathan |
||||||
#919 | Permission error | Bug report | normal | FileZilla Server | worksforme | ||
Description |
http://img342.imageshack.us/img342/1505/ftp6ip.jpg users can create folders when it isn't permitted. They got a permmission error message but the folder is created anyway. Log is at : http://mavromatis.moved.in/mavs/FileZilla Server.log Thanks |
||||||
#920 | MDTM 550 Error | Bug report | normal | FileZilla Server | |||
Description |
It appears that MDTM is only partially implemented. ? 'MDTM<sp>filename' returns a correct timestamp, but 'MDTM<sp>timestamp<sp>filename' returns '500 File not found' instead of changing the timestamp on the server. That is the key to the MDTM function -- update the timestamp on the server. Since the FEAT command reports MDTM implementation, I assume this is a bug. |
||||||
#924 | Use Of Source Port 22 On Non-Secure FTP Data Connection | Bug report | normal | FileZilla Server | |||
Description |
I'm using FileZilla Server 0.9.9. The first active mode transfer I initiate behaves normally: the data connection is made from the server to the client with the source port of 20. While that first transfer is running, the next transfer fails, as follows: The initial data connection packet is sent from the server to the client with the source port of 22 and a random destination port (typically set with the PORT command). But the return packet, which has a destination port of 22 because that's what Filezilla chose, is blocked by our firewall because we do not allow traffic on the SSH port (according to IANA, at http://www.iana.org/assignments/port-numbers). I shouldn't have to open a port in our firewall (even for just established-connection traffic) where a known service might be running. Here are Filezilla logs for this scenario; I'm using the Windows command-line FTP client. (000012) 7/29/2005 12:26:24 PM - (not logged in) (70.20.144.155)> Connected, sending welcome message... (000012) 7/29/2005 12:26:24 PM - (not logged in) (70.20.144.155)> 220-FileZilla Server version 0.9.9 beta (000012) 7/29/2005 12:26:24 PM - (not logged in) (70.20.144.155)> 220-written by Tim Kosse (Tim.Kosse@…) (000012) 7/29/2005 12:26:24 PM - (not logged in) (70.20.144.155)> 220 Please visit http://sourceforge.net/projects/filezilla/ (000012) 7/29/2005 12:26:27 PM - (not logged in) (70.20.144.155)> USER theplatform (000012) 7/29/2005 12:26:27 PM - (not logged in) (70.20.144.155)> 331 Password required for theplatform (000012) 7/29/2005 12:26:29 PM - (not logged in) (70.20.144.155)> PASS (000012) 7/29/2005 12:26:29 PM - theplatform (70.20.144.155)> 230 Logged on (000012) 7/29/2005 12:26:31 PM - theplatform (70.20.144.155)> TYPE I (000012) 7/29/2005 12:26:31 PM - theplatform (70.20.144.155)> 200 Type set to I (000012) 7/29/2005 12:26:41 PM - theplatform (70.20.144.155)> PORT 70,20,144,155,19,137 (000012) 7/29/2005 12:26:41 PM - theplatform (70.20.144.155)> 200 Port command successful (000012) 7/29/2005 12:26:41 PM - theplatform (70.20.144.155)> STOR 2005_0709Image0157.AVI (000012) 7/29/2005 12:26:41 PM - theplatform (70.20.144.155)> 150 Opening data channel for file transfer. (000013) 7/29/2005 12:28:22 PM - (not logged in) (70.20.144.155)> Connected, sending welcome message... (000013) 7/29/2005 12:28:22 PM - (not logged in) (70.20.144.155)> 220-FileZilla Server version 0.9.9 beta (000013) 7/29/2005 12:28:22 PM - (not logged in) (70.20.144.155)> 220-written by Tim Kosse (Tim.Kosse@…) (000013) 7/29/2005 12:28:22 PM - (not logged in) (70.20.144.155)> 220 Please visit http://sourceforge.net/projects/filezilla/ (000013) 7/29/2005 12:28:38 PM - (not logged in) (70.20.144.155)> USER theplatform (000013) 7/29/2005 12:28:38 PM - (not logged in) (70.20.144.155)> 331 Password required for theplatform (000013) 7/29/2005 12:28:48 PM - (not logged in) (70.20.144.155)> PASS (000013) 7/29/2005 12:28:48 PM - theplatform (70.20.144.155)> 230 Logged on (000013) 7/29/2005 12:28:58 PM - theplatform (70.20.144.155)> PORT 70,20,144,155,19,138 (000013) 7/29/2005 12:28:58 PM - theplatform (70.20.144.155)> 200 Port command successful (000013) 7/29/2005 12:29:02 PM - theplatform (70.20.144.155)> LIST (000013) 7/29/2005 12:29:02 PM - theplatform (70.20.144.155)> 150 Opening data channel for directory list. (000013) 7/29/2005 12:29:12 PM - theplatform (70.20.144.155)> 425 Can't open data connection. Here are the pertinent firewall log entries; list 101 is inbound packets, and list 102 are outbound packets; all permitted packets are non-established (i.e. connection- initiating): Fri Jul 29 12:26:25 2005 <190>858383: %SEC-6- IPACCESSLOGP: list 101 permitted tcp 70.20.144.155 (3858) -> 198.181.237.7(21), 1 packet Fri Jul 29 12:26:42 2005 <190>858387: %SEC-6- IPACCESSLOGP: list 102 permitted tcp 198.181.237.7 (20) -> 70.20.144.155(5001), 1 packet Fri Jul 29 12:28:19 2005 <190>858398: %SEC-6- IPACCESSLOGP: list 101 permitted tcp 70.20.144.155 (3879) -> 198.181.237.7(21), 1 packet Fri Jul 29 12:29:02 2005 <190>858403: %SEC-6- IPACCESSLOGP: list 102 permitted tcp 198.181.237.7 (22) -> 70.20.144.155(5002), 1 packet Fri Jul 29 12:29:07 2005 <190>858406: %SEC-6- IPACCESSLOGP: list 101 denied tcp 70.20.144.155 (5002) -> 198.181.237.7(22), 1 packet |
||||||
#926 | Admin password | Bug report | normal | FileZilla Server | outdated | ||
Description |
Hello, FileZilla server doesn't ask for admin password for administration interface when connecting from local machine. I want to run FileZilla server on Terminal Server, so everyone could admin the server without password supplied. Regards, VooDooMan |
||||||
#929 | Security issue: Invalid folder names created in file system | Bug report | normal | FileZilla Server | |||
Description |
This seems to be an issue that should at least have an option available to block invalid folder/files from being created in the servers file system. Here is an example of the folder names that were created (full log file also attached): (000025) 8/11/2005 16:44:46 - anonymous (84.97.64.36)> MKD uploads/ /ÿÿk 97536ÿÿÿÿÿÿÿÿÿÿ/ (000025) 8/11/2005 16:44:46 - anonymous (84.97.64.36)> 257 Directory created successfully (000025) 8/11/2005 16:44:46 - anonymous (84.97.64.36)> MKD uploads/ /ÿÿk 97536ÿÿÿÿÿÿÿÿÿÿ/ÿÿÿÿÿÿÿÿÿt 22241ÿÿÿÿ/ (000025) 8/11/2005 16:44:46 - anonymous (84.97.64.36)> 257 Directory created successfully (000025) 8/11/2005 16:44:46 - anonymous (84.97.64.36)> MKD uploads/ /ÿÿk 97536ÿÿÿÿÿÿÿÿÿÿ/ÿÿÿÿÿÿÿÿÿt 22241ÿÿÿÿ/ÿÿÿÿÿÿÿÿÿP 63612ÿÿÿÿÿÿÿÿÿÿ/ (000025) 8/11/2005 16:44:46 - anonymous (84.97.64.36)> 257 Directory created successfully Note that folders were created with spaces thruout the name were created. Attempting to delete these folders via standard windows file managers cause errors. Only method I was able to find to delete the folders was to use rmdir from command prompt on the parent folder (uploads). Thanks, David Troesch |
||||||
#935 | Admin password plaintext | Bug report | normal | FileZilla Server | |||
Description |
Why is the Admin password in plaintext? Why isn't crypted like the user passwords (in md5)? Please encrypt this ADMIN password. Thanks. |
||||||
#938 | FileZilla weakly-encrypted password vulnerability (?) | Bug report | normal | FileZilla Server | |||
Description |
..I didn't see any news or other information on the SF site, so I'm forwarding this for the developers: http://lists.grok.org.uk/pipermail/full-disclosure/2005-September/036775.html (or, http://tinyurl.com/8adcf) I'm not a programmer/coder so I couldn't check the POC for myself, but I wanted to pass this on to the developers of Filezilla. p.s.: Great app, besides all this. Keep Coding! X |
||||||
#939 | 0.9.10 Failed to load SSL libraries | Bug report | normal | FileZilla Server | |||
Description |
After a upgrade from the previous version. Had to replace the new versions of the libeay32 and ssleay32.dll's with the old ones from the 0.9.9 release i guess to get it up and running again. |
||||||
#940 | 0.9.10 Failed to load SSL libraries | Bug report | normal | FileZilla Server | worksforme | ||
Description |
After a upgrade from the previous version. Had to replace the new versions of the libeay32 and ssleay32.dll's with the old ones from the 0.9.9 release i guess to get it up and running again. |
||||||
#948 | 450 error when home directory is mapped network drive | Bug report | normal | FileZilla Server | |||
Description |
Using FileZilla server 0.9.10 beta. Works fine when user home directory is on a local drive. However, simply changing directory to R:, for example, which is a mapped network drive (mapped with different user name which is a domain\user for user and password), the server always gets error 450, cannot access file. Same error is reported at client system. I am able to copy files into this mapped network drive, so there doesn't SEEM to be an access problem. |
||||||
#951 | Dummy shared folder entry | Bug report | normal | FileZilla Server | outdated | ||
Description |
Inside "User Accounts" dialog - "Shared Folders" section, if you click add and then "Cancel" to folder browser, <new directory> entry still remains on "Shared Folders" list. Can be cleared by "Remove" button. It doesn't cause any error, but simply a bug. |
||||||
#952 | Compiling with Visual C++ 2005 | Bug report | normal | FileZilla Server | |||
Description |
Compiling FZ Server (0.9.10a) with Visual C++ 2005 Express Beta Edition. Due to future changes in the compiler, i.e. Visual C++ 2005, default type "int" is no longer implied and must be declared. "error C4430: missing type specifier - int assumed. Note: C++ does not support default-int" See "Breaking changes in Visual C++ 2005 ..." To compile 0.9.10a with Visual C++ 2005, edit CControlSocket.cpp line 2766, and add "int" to the beginning of the line. <font color=red>int</font> CControlSocket::CreateTransferSocket(... The interface does not compile due to missing MFC header files that I have not been able to locate. So far afxdhtml.h is causing a fatal error: This is probably due to the beta version. You’ll probably want to keep this new coding standard in mind while you're writing updates etc, to avoid this error at a later date. Glen PS. Nice Work. |
||||||
#965 | problem special character | Bug report | normal | FileZilla Server | |||
Description |
Sorry for my english In transfer to the server filezilla in special character as ñ Ñ in the name of files or folders the filezilla changes de name (españa to espaa). Because this error the client aplication crast (bloq). bye |
||||||
#967 | logging screen win nt | Bug report | blocker | FileZilla Server | |||
Description |
Hi, on Windows NT 4.0 i can't see correctly the log in the filezilla server interface. The whole Logging Line are display on the same line. I have try several version of filezilla server ( also the latest ) and i have the pb. I have also try this on several pc always under win nt 4. |
||||||
#970 | command "CWD ~" failed (+ possible solution) | Bug report | low | FileZilla Server | |||
Description |
The Opera Internet Browser before changing dir always send "CWD ~" first. And expect after that is current dir changed to home dir ("/"). But FileZilla said: "550 CWD failed. '/<current dir>/~': directory not found. " I think in file 'Permission.cpp' in begining of function 'CStdString CPermissions::CanonifyServerDir(CStdString currentDir, CStdString newDir) const' should be added next code: ------------------------------ if (newDir == "~") {
}; ----------------------------- |
||||||
#979 | FileZilla Server fails to list network drives. | Bug report | normal | FileZilla Server | outdated | ||
Description |
It seems like FileZilla Server fails to list network drives. I have added some network drives to my shared folders. I have tried to map them both to the drive letter and to the unc-path without any luck. If I configure it like this: Directory: Y: (wich is a network drive) Alias: C:\<HomeDir>\AliasForNetworkDir then the AliasForNetworkDir-folder is shown up in my homedir catalog, but when I enter that folder none of it's files or subfolders are listed. |
||||||
#981 | Passwords with spaces | Bug report | normal | FileZilla Server | |||
Description |
Hello, i can not set a user password with a space at begin or end like " 123" or "456 " in "FileZilla Server version 0.9.10 beta" A space in the middle like "123 456" is working. Maybe you make something like a trim() on this values? I don't know if other values are also effected. Best regards, Carsten Wiedmann |
||||||
#983 | Broken link in server GUI | Bug report | normal | FileZilla Server | |||
Description |
In the FileZilla Server Option > Filetransfer compression, the URL given to get more detail about the compression method is broken. http://www.ietf.org/internet-drafts/draft-preston-ftpext-deflate-02.txt |
||||||
#984 | Installing commercial SSL cert hangs FZS @ 100% CPU usage | Bug report | high | FileZilla Server | |||
Description |
To reproduce: Generate a certificate signing request (CSR). Example with openssl:
Give the private key a password of "test". For this example, the corresponding private key will be dropped in the current directory as "privkey.pem". Note the location of this file. Use the CSR you just created to obtain a Thawte trial SSL certificate for free: Paste in the text from the certreq.txt file, and save the resultant certificate text in a new file, certnew.pem. Pull up the FileZilla server interface. Access Edit -> Settings. Click SSL/TLS settings. Click Enable SSL/TLS support. Enter the full path to privkey.pem in the "Private key file" field. Enter the full path to the new Thawte trial certificate in the "Certificate file" field. Press OK. Filezilla server interface hangs, and consumes 100% of CPU. Interface must be force-killed. Version: Filezilla server 0.9.10a Platform: Windows Server 2003. |
||||||
#985 | 0.9.10a is slow | Bug report | normal | FileZilla Server | |||
Description |
I used FileZilla server 0.9.9 under XP Professional and it works fine. On the same system Version 0.9.10a is really slow (transfer rate ~ 70 Kbytes/sec). |
||||||
#986 | Request change to IP Filter priority handling | Feature request | high | FileZilla Server | worksforme | ||
Description |
It seems you can set a IP Filter on 3 different levels Server, Group and User One would guess that user would bypass group and group would bypass server settings but thats not working. From my experiences User bypass Group but Group/User does not bypass Server settings |
||||||
#987 | Request change in Speed Limit priority between user, server and group. | Feature request | high | FileZilla Server | worksforme | ||
Description |
It seems you can set a Speed Limits on 3 different levels Server, Group and User One would guess that user would bypass group and group would bypass server settings but thats not working. From my experiences User bypass Server but not Group. I havent tested if Group bypass Server but this may not work either. |
||||||
#989 | Files beginning with " - " Will Not Download | Bug report | normal | FileZilla Server | |||
Description |
Filezilla server will list the files that begin with "
download them via Filezilla client, you receive the following message: Command: RETR - Dear Mama.mp3 Response: 550 File not found Error: Download failed Not sure if this is a limitation of the FTP protocol or not, but it seems like it should be easy to resolve. |
||||||
#994 | Retrieving external IP address broken? | Bug report | normal | FileZilla Server | |||
Description |
Perhaps you can check this. Yesterday I upgraded Filezilla Server from 0.9.9 to 0.9.11. The new software seems not any more to be able to retrieve a new IP address from http://checkip.dyndns.org in the "Passive mode" settings, though 0.9.9 had no problems with that!?! Entering this address in the "Retrieve external IP address from" edit line has no effect - if a client connects in passive mode and tries to retrieve the directory or a file, the server always tells sth. like "227 Entering Passive Mode (192,168,0,2,23,33)", what is clearly not the address returned by the website... :( Auf bai...
|
||||||
#995 | invalid 'no-transfer' timeout on server | Bug report | normal | FileZilla Server | |||
Description |
'No transfer timeout' is set to the default 120s on this 0.9.11 Filezilla server, running on W2K, yet it seems to disconnect clients a lot more quickly - see examples below for 3 seconds and 4 seconds. Is this something to do with two users signed in with the same id? (ratrunner1). I have had to disable 'no transfer timeout' (i.e. 0) to stop this from happening. (000110) 07/12/2005 11:04:41 - ratrunner1 (194.62.232.125)> 257 "/" is current directory. (000110) 07/12/2005 11:04:41 - ratrunner1 (194.62.232.125)> MDTM 3G_FTP_2MB.mp3 (000110) 07/12/2005 11:04:41 - ratrunner1 (194.62.232.125)> 213 20050215180742 (000109) 07/12/2005 11:04:41 - ratrunner1 (194.62.232.126)> PWD (000109) 07/12/2005 11:04:41 - ratrunner1 (194.62.232.126)> 257 "/" is current directory. (000109) 07/12/2005 11:04:41 - ratrunner1 (194.62.232.126)> MDTM 3G_FTP_2MB.mp3 (000109) 07/12/2005 11:04:41 - ratrunner1 (194.62.232.126)> 213 20050215180742 (000109) 07/12/2005 11:04:44 - ratrunner1 (194.62.232.126)> 421 No-transfer-time exceeded. Closing control (000110) 07/12/2005 11:07:52 - ratrunner1 (194.62.232.125)> 257 "/" is current directory. (000110) 07/12/2005 11:07:52 - ratrunner1 (194.62.232.125)> MDTM 3G_FTP_2MB.mp3 (000110) 07/12/2005 11:07:52 - ratrunner1 (194.62.232.125)> 213 20050215180742 (000111) 07/12/2005 11:07:52 - ratrunner1 (194.62.232.126)> PWD (000111) 07/12/2005 11:07:52 - ratrunner1 (194.62.232.126)> 257 "/" is current directory. (000111) 07/12/2005 11:07:52 - ratrunner1 (194.62.232.126)> MDTM 3G_FTP_2MB.mp3 (000111) 07/12/2005 11:07:52 - ratrunner1 (194.62.232.126)> 213 20050215180742 (000110) 07/12/2005 11:07:56 - ratrunner1 (194.62.232.125)> 421 No-transfer-time exceeded. Closing control |
||||||
#1001 | *ULTRA* minor bug | Bug report | normal | FileZilla Server | |||
Description |
I noticed when I was FTPing files between two computers on my 100mbit LAN that on the server side of things, its showing the current throughput, but, when it reaches to over 1000, it places the comma in the wrong spot. Instead of 1,000, its showing 10,00kb/s. Quick fix, but not worthy of a new release. ;) |
||||||
#1016 | Speedlimit Settings confusing | Bug report | normal | FileZilla Server | |||
Description |
At least at my version (0.9.12c) the Speed-Limit settings page (At the Server-Settings dialogue) is totaly nonsense. When I want to limit the outgoing bandwith of the server I have to limit the "download" speed and to cap the incomping line I have to set a "upload" limit. Seen from the client's side, it is totally correct but seen from the server's side it is just confusing. Perhabs the correct naming should be "Speed-Limit (Outgoing)" and "Speed-Limit (Incoming)". Using the terms Upload/Download is just confusing. |
||||||
#1032 | SMB Aliases are not saved | Bug report | normal | FileZilla Server | fixed | ||
Description |
in a Group I am using a SMB-Folder as home dir. if I will use a Alias with that Folder it seems to be unsaved because after restart the PC and the ftp server this properties does not exist. |
||||||
#1037 | FileZilla Server 0.9.13b crashing | Bug report | normal | FileZilla Server | |||
Description |
I recently upgraded to FileZilla Server 0.9.13b, and it has crashed on me twice, once during a transfer, and once when logging in as admin (altho my FileZilla Server Interface is set to only start when run manually). One of the times was in the middle of a file transfer, and I got a prompt asking if I wanted to send information somewhere, but I couldn't tell what information, so I said no; I couldn't figure out how to tell what information it wanted to send. I just ran the FileZilla Server interface, but I don't see where to get the log file? I don't see it on the ? menu, or the File menu, or the Server menu. I drilled into Edit/Settings/Logging, but logging is disabled. Does that mean there is no log of the crashes? I'd like to rollback to FileZilla Server 0.9.13a, but I don't know how to download it -- or should I rollback to 0.9.12c (which is available in the download list)? |
||||||
#1041 | incomplete chinese support for directory names | Bug report | normal | FileZilla Server | |||
Description |
I've been using FileZilla Server for a long time, and this bug really bothers me. Many directories named in Chinese cannot be seen under FileZilla Server 0.9.13b or order versions. I've tested 0.9.1~0.9.13b, and 0.9.1 seems to be better than 0.9.13b. Some characters can be seen under 0.9.1, though files are not downloadable. (server replies File Not Found) Example directory names: æˆæœå±• 國科會 I have tried clients from Unix(FreeBSD) ftp client ,FileZilla to IE. Thanks a lot. |
||||||
#1046 | implicit SSL not understood | Bug report | normal | FileZilla Server | |||
Description |
Filezilla server either receives bad implicit SSL syntax from the filezilla client, or doesn't support implicit SSL connection properly. (using filezilla client 2.2.19a and server .9.14a) The "force explicit SSL" setting is NOT selected. Server log... (000027) 3/30/2006 13:49:26 PM - (not logged in) (12.32.203.32)> Connected, sending welcome message... (000027) 3/30/2006 13:49:26 PM - (not logged in) (12.32.203.32)> 220 on MNOL (000027) 3/30/2006 13:49:26 PM - (not logged in) (12.32.203.32)> €‚ (000027) 3/30/2006 13:49:26 PM - (not logged in) (12.32.203.32)> 500 Syntax error, command unrecognized. (000027) 3/30/2006 13:49:26 PM - (not logged in) (12.32.203.32)> i (000027) 3/30/2006 13:49:26 PM - (not logged in) (12.32.203.32)> 500 Syntax error, command unrecognized. (000027) 3/30/2006 13:49:26 PM - (not logged in) (12.32.203.32)> (000027) 3/30/2006 13:49:26 PM - (not logged in) (12.32.203.32)> 500 Syntax error, command unrecognized. (000027) 3/30/2006 13:49:26 PM - (not logged in) (12.32.203.32)> 9 (000027) 3/30/2006 13:49:26 PM - (not logged in) (12.32.203.32)> 500 Syntax error, command unrecognized. (000027) 3/30/2006 13:49:26 PM - (not logged in) (12.32.203.32)> 8 (000027) 3/30/2006 13:49:26 PM - (not logged in) Client log... Status: Connecting to myserver ... Status: Connected with myserver, negotiating SSL connection... Error: Can't establish SSL connection Error: Disconnected from server Error: Unable to connect! Status: Waiting to retry... (5 retries left) |
||||||
#1052 | central european characters | Bug report | normal | FileZilla Server | |||
Description |
Hi! I'm unable to download files from FileZilla Server that contains central european character "Å " in filename. I've attached log from FileZilla Client so You can take a better look in this problem. Best Regards! otrov |
||||||
#1056 | Protocol error: Invalid data | Bug report | normal | FileZilla Server | |||
Description |
I got this error in the FileZilla Server Interface, trying to add a home directory for the new user I just added: Sending account settings, please wait... Protocol error: Invalid data, could not import account settings. Could not change account settings (Also, note that ctrl-c seems to be broken when trying to copy error text out of the output window.) (Also, the version in the About window doesn't seem to be copyable -- I was going to copy it and paste it in here.) 0.9.14a b |
||||||
#1057 | ctrl-c not working in output window | Bug report | normal | FileZilla Server | |||
Description |
ctrl-c seems to be broken when trying to copy error text out of the output window. (Also, the version in the About window doesn't seem to be copyable -- I was going to copy it and paste it in here.) 0.9.14a b |
||||||
#1064 | Chinese Characters Don't Display correctly (WindowsXPSP2CHS) | Bug report | normal | FileZilla Server | |||
Description |
When using the latest version Filezilla Server 0.9.15, Chinese characters display as clobber in the client which does not support utf-8 (flashfxp) but display correctly in Internet Explorer. |
||||||
#1066 | Garbled Directory for Traditional Chinese in 0.9.15 server | Bug report | normal | FileZilla Server | |||
Description |
FTP Server: Filezilla 0.9.15 FTP Client: Filezilla 2.2.22 After upgrading the ftp server from 0.9.14a to 0.9.15, filezilla client can't see properly displayed traditional chinese directories. All traditional chinese directories are garbled. It shows "??????.avi", etc. Prior to 0.9.14a (including 0.9.14a) has no garbled directory issue. |
||||||
#1067 | something wrong with the Filezilla Server Setting | Bug report | normal | FileZilla Server | fixed | ||
Description |
In the miscellaneous options of filezilla server, the option " Allow downloading of files which are open for writing by another process" can not work correctly. After unchecking it, when i open it again the option is checked. |
||||||
#1068 | 0.9.16 SSL (explicit) does not work | Bug report | normal | FileZilla Server | |||
Description |
Needed an FTP server, which support ftps, was in a hurry and tried FZ. Got 0.9.15 and it seemed to do fine except with the only client that really mathered - Thumbleweed's SecureTransport (widely used in big companies, banks, etc.) So tonight I saw that there's 0.9.16 out there and decided to give it a try. Well, now all the clients (FZ, SmartFTP, SecureTransport, FTPVoyager) don't work at all. There's the log from FZ client: Status: Connecting to localhost ... Trace: FtpControlSocket.cpp(5083): m_pSslLayer changed state from 0 to 1 caller=0x003aa7bc Trace: FtpControlSocket.cpp(5083): m_pSslLayer changed state from 1 to 2 caller=0x003aa7bc Trace: FtpControlSocket.cpp(5083): m_pSslLayer changed state from 2 to 4 caller=0x003aa7bc Trace: FtpControlSocket.cpp(938): OnConnect(0) OpMode=1 OpState=-8 caller=0x003aa7bc Status: Connected with localhost, negotiating SSL connection... Trace: FtpControlSocket.cpp(761): OnReceive(0) OpMode=1 OpState=-8 caller=0x003aa7bc Response: 220-FileZilla Server version 0.9.16 beta Response: 220-written by Tim Kosse (Tim.Kosse@…) Response: 220 Please visit http://sourceforge.net/projects/filezilla/ Command: AUTH SSL Trace: FtpControlSocket.cpp(761): OnReceive(0) OpMode=1 OpState=-9 caller=0x003aa7bc Response: 2 Response: 3 Response: 4 Response: Response: U Response: s Response: i Response: n Response: g Response: Response: a Response: u Response: t Response: h Response: e Response: n Response: t Error: Timeout detected! |
||||||
#1076 | Local IP send to client in passive mode and SSL | Bug report | normal | FileZilla Server | |||
Description |
This one took me awhile to track... "Passive mode settings" When using SSL and being behind a firewall, if "Default" or "Retrieve External IP from:" are chosen, then the server will send back to the client its local IP address instead of the external one (even though http://filezilla.sourceforge.net/misc/ip.php returns the external IP just fine). The client tries to establish data connection using this local IP and of course fails. The only option that works is "Use the following IP:" |
||||||
#1077 | Admin interface cannot connect to a remote server | Bug report | normal | FileZilla Server | |||
Description |
Just as the summary says. Local network, FZS running on one machine, Admin interface launched from another can't access it. With or without password. No firewall etc. While looking with netstat (I know, I know, but this is the only thing I have here) I can't see it making a connection. Also when launching the server interface and pointing to the local machine (127.0.0.1) the wordage on the dialog box suggests that you have to type the password only if you're connecting to a remote server. Which is not true. The password needs to be typed for local connection too. |
||||||
#1083 | no aliases on MLSD | Bug report | normal | FileZilla Server | |||
Description |
It seems to exist two ability to transfer directory listing to client, LIST and MLST/MLSD. I have one client, that uses default MLSD and then FileZilla don't transfer aliases (like /filegroup1) defined for user. With LIST are all directories showed. I don't know very good this funktions and the kind FileZilla use aliases, but I think this is a bug of FileZilla. P.S.: Tested with FileZilla Server 0.9.17 beta and UTF- 8 |
||||||
#1099 | FileZilla 0.9.18 installation lost or scrambled passwords | Bug report | normal | FileZilla Server | |||
Description |
Now my clients cannot log in. The solution is to set the passwords in FileZilla Interface on the server to the passwords to what they have been up until now. My conclusion is that the uninstall/upgrade from 0.9.17 to 0.9.18 lost or scrambled the server's copies of passwords. |
||||||
#1100 | Listen to SSL/TSL-connections feature seems to be broken | Bug report | normal | FileZilla Server | |||
Description |
Hello, I have been instructed by the developer from "2brightsparks" (the SyncBackSE backup tool developers) to contact you about this issue. What is going on is that when I activate the "Use implicit connection (port 990)" in SyncBackSE I get an error message like this on the client (SyncBackSE) side: "Connect failed: SSL/TSL (18):.Please check your FTP settings and network connection" And on the server side on the console I see the following: (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> Connected, sending welcome message... (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 220-FileZilla Server version 0.9.18 beta (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 220-written by Tim Kosse (Tim.Kosse@…) (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 220 Please visit http://sourceforge.net/projects/filezilla/ (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> €L (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 3 (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> € (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> À (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> € (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> @ (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> d (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> b (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> € (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> € (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> 500 Syntax error, command unrecognized. (000002) 5/31/2006 7:50:13 AM - (not logged in) (192.168.1.100)> disconnected. The SyncBackSE developer, Michael J. Leaver, looked at the above report and he replied the following: "With 0.9.16c beta I could not reproduce this issue, but on newer versions of Filezilla it does fail. ... Please contact Filezilla support to get the issue resolved." That is why I am filing this bug report. Thank you, Silvian |
||||||
#1103 | server v0.9.18 time zone issues | Bug report | normal | FileZilla Server | |||
Description |
I use syncbackSE to synchronize files. With version 0.9.18 server, it now seems to be mis-reporting the timezone, since the reported filetimes are off by -7hrs. Thanks! |
||||||
#1105 | error in non-English chars listing | Bug report | normal | FileZilla Server | |||
Description |
in FileZilla Server 0.9.15 and later, if the name of a file/dir contains non-English chars (in my case, Simplified Chinese encoded in GBK using Windows XP CodePage 936), these chars become question marks "?". This problem was not found in 0.9.12c (maybe 0.9.14 will work too) and earlier versions. |
||||||
#1112 | FireZilla incorrectly parsing FTP protocol out of TCP packet | Bug report | normal | FileZilla Server | |||
Description |
Using the Perl ftp interface Net::FTP, I created a script to automaticly upload files to an FTP server running FireZilla 0.9.18b. Right now this server is incorrectly receiving the FTP requests from my client.
192,168,1,101,13,94" where my FTP client says its sending "PORT 192,168,1,101,13,94". The missing first letter is confirmed to be a FireZilla parsing problem because I used Ethereal to monitor the traffic and indeed, PORT is being sent. |
||||||
#1141 | problems with characters åäö | Bug report | normal | FileZilla Server | |||
Description |
The characters åäö (latin1/sv_SE) isn't displayed correctly using Flashfxp (and I bet many other clients aswell). They are displayed correctly using the FileZilla Client thought. Flashfxp is a client many people use, and for that reason I think it should be supported by the FileZilla Server to display non-US characters correctly. Even the ones that doesn't support RFC 2640. Keep up the good work! :-) |
||||||
#1142 | "Allow downloading files.." check box doesn't work | Bug report | normal | FileZilla Server | |||
Description |
In Settings->Miscellanous checkbox "Allow downloading files witch are open for writing by..." doesn't work. Sometimes it checked and sometimes not. I check it and just click OK, and then I load settings again sometimes it checked and sometimes not. |
||||||
#1143 | Server crashed 0.9.12 | Bug report | normal | FileZilla Server | |||
Description |
Exception report created by FileZilla Server version 0.9.12 beta =================================================== System details: Operating System: Microsoft Windows XP Professional Service Pack 2 (Build 2600) Processor Information: Vendor: GenuineIntel ,Speed: 2666MHz ,Type: Intel Pentium compatible,Number Of Processors: 1 ,Architecture: Intel ,Level: Unknown 15 ,Stepping: 10-25 Memory Information: Memory Used 32%, Total Physical Memory 916720KB, Physical Memory Available 618988KB, Total Virtual Memory 2097024KB, Available Virtual Memory 2065492KB, Working Set Min : 200KB Max : 1380KB . Exception Details: Exception code: C0000005 ACCESS_VIOLATION Fault address: 00409810 01:00008810 d:\Program Files\FileZilla Server\FileZilla Server.exe Call stack: Address Frame Function SourceFile 00409810 77D18C1A 0001:00008810 d:\Program Files\FileZilla Server\FileZilla Server.exe 0300BA00 0011C5B8 |
||||||
#1158 | Very slow response | Bug report | normal | FileZilla Server | |||
Description |
on ftp client (Mac OS X 10.3.9) on local network, issued command "mget *" (directory contained about 20 files), the server responded ... (000006) 02/09/2006 15:27:25 - andy (192.168.0.53)> 229
(000006) 02/09/2006 15:28:40 - andy (192.168.0.53)> EPRT |1|192.168.0.53|49243| (000006) 02/09/2006 15:28:40 - andy (192.168.0.53)> 200 Port command successful i.e. 75 seconds before anything happened appparently! Even then, nothing appeared on the client and I went off to do something else and the session had timed out before I came back. This wait could be improved. |
||||||
#1173 | SSL - directory listing unreliable | Bug report | normal | FileZilla Server | |||
Description |
Hi there, I see this very often when running FZ client against the FZ server (implicit SSL). Not just the last version (19) - it has always been like that. Many times when I click on a directory it would wait for several seconds just to came back with "Could not retrieve directory listing". Refresh - and it does it just fine. Locally or over the Internet. This might not be a big issue when using a GUI client and you're in front of the computer all the time, but it's a real problem if it should be done from an unattended program. I'm currently evaluating IP*Works! SSL (http://www.nsoftware.com/ipworks/ssl/default.aspx) and it seems to always have the problem, which basically renders it unusable with FileZilla. Also - don't know if it's related to the above, but it also seems that the file transfer under SSL is not very reliable either. Even with a (supposedly) good connection, when I have multiple files in the queue I get a lot (looks like) of transfer errors and eventually some files won't get over, because the number of errors reached the limit. Again - not a huge deal if you're at the console all the time, but quite unusable for "set it and forget it" kind of mode... Keep up the good work! --IK |
||||||
#1179 | Active mode data connection is made from the wrong port | Bug report | normal | FileZilla Server | |||
Description |
According to the FTP specification (RFC0959), in active FTP mode, the data connection should be made from port L-1, where L is the port that the server is listening for control connections (see section 3.2 Establishing Data Connections, paragraph 1). This should be true for every active mode transfer. FileZilla Server attempts to bind the outgoing port as per specification, but fails to do this when another active mode data connection exists. The second connection will get port L+1, and if a third connection is opened, then it will get an arbitrary OS-assigned port. Versions:
0.9.4, 0.9.8a, 0.9.19)
To reproduce:
host to the same server host.
-n" on the client host. Expected behavior:
port 21.
Observed behavior:
port 21.
unspecified port. Cause:
requested local port is already used by another socket.
setsockopt(socket, SOL_SOCKET, SO_REUSEADDR, ...) call, passing TRUE as the option value, before binding the socket. |
||||||
#1180 | Server hangs client if initial directory contains no files. | Bug report | normal | FileZilla Server | |||
Description |
When using FileZilla client to look at a FileZilla server, if the initial directory contains no files, it generates an error that says "Could not retrieve directory listing" and the server generates an error that says "425 can't open data connection." This seems to only happen when the initial source directory on the server is empty (ie, there are sub- folders in the directory, but there are no files at that directory level). |
||||||
#1184 | FZ server and IP*Works | Bug report | normal | FileZilla Server | |||
Description |
I was evaluating the IP*Works component and found it not to work with FZ server in FTP implicit mode. The guys at IP*Works responded right away and tried to research the issue. There's what they said: " Our developers have done some more research on this issue, and there are some problems here that appear to be with the server. Since it is still in beta, this is not very surprising. In Explicit mode on upload, the component simply closes the data connection but the server reports a 426 FTP error. I'm not sure why the server is doing this, since the component is performing the appropriate action. In Implicit, it appears that the server is not even responding to the SSL handshake for the data connection. At this point, there is nothing that can be done within the component to accommodate this server. Hopefully when the server is no longer in Beta, these issues will have been resolved. At that time, if there are still some other problems, we will be happy to investigate them. You may also consider reporting these errors to the makers of the FTP server for their input and consideration. " Any comments? |
||||||
#1187 | rights upload problem | Bug report | normal | FileZilla Server | |||
Description |
I use Filezilla server 0.9.19 (I have installed the lastest version today) and Windows XP pro. I have two accounts. Admin a Power User. I installed filezilla as admin and I use it in Power user account. Sometime when somebody upload me a file, I don't have right to delete it from my disk. I need to login as admin and delete it. |
||||||
#1190 | Cannot use Chinese in user description | Bug report | normal | FileZilla Server | |||
Description |
I'm using FileZilla Server v0.9.20 on Windows XP SP2. In "Shared Folders", I can use Chinese in both directories and aliases. However, if I add a new user in "Users", type some Chinese characters in the description and click OK, then I get the following error message and the user is not added.
Steps to reproduce:
If I modify "FileZilla Server.xml" directly and restart the service, I get the following message when I want to enter the "Users" setting.
Steps to reproduce:
<User Name="test"> <Option Name="Pass"/> <Option Name="Group"/> <Option Name="Bypass server userlimit">0</Option> <Option Name="User Limit">0</Option> <Option Name="IP Limit">0</Option> <Option Name="Enabled">1</Option> <Option Name="Comments">ä¸æ–‡</Option> <Option Name="ForceSsl">0</Option> <IpFilter> <Disallowed/> <Allowed/> </IpFilter> <Permissions/> <SpeedLimits DlType="0" DlLimit="10" ServerDlLimitBypass="0" UlType="0" UlLimit="10" ServerUlLimitBypass="0"> <Download/> <Upload/> </SpeedLimits> </User>
|
||||||
#1191 | Certain clients disconnect or stall | Bug report | normal | FileZilla Server | |||
Description |
I run an FTP server with FileZilla Server (currently on 0.9.20 on Windows Server 2003 SP1). Users use a great variety of clients to connect, and I have found that some have trouble with the service FileZilla offers. Sometimes, for little apparent reason, a client will not be able connect after it issues a PASV command. It appears to hang, as though it is expecting something further from the server. One such client is Bulletproof FTP 2.58 under Windows. A trial version can be downloaded from bpftp.com . I have attached the logs that I have on the server end and what the client reports. After connecting and authenticating, the client issues PASV and then hangs. The server reports that it disconnects, but the client behaves as though it is still connected and is expecting a response to the PASV command. |
||||||
#1195 | Directory list with file pattern odd problem | Bug report | normal | FileZilla Server | |||
Description |
I'm writing a piece of software that should do FTP(s) download/upload using /n Software's "IPWorks! SSL V6" and FZ (running the latest 0.9.20) Server as a test platform. (There was an issue with the component not sending PROT in ImplicitSSL mode, which was solved by an undocumented setting in IP!Works. SSL) Here's another one and I'm not sure if the problem is in IPWorks or FZ. From what I see in the FZ log I thing there’s a good chance that it’s actually a bug in FZ…
There's a snapshot from the console: (000021) 11/27/2006 16:20:43 PM - ftpuser (127.0.0.1)> PASV (000021) 11/27/2006 16:20:44 PM - ftpuser (127.0.0.1)> 227 Entering Passive Mode (127,0,0,1,117,48) (000021) 11/27/2006 16:20:44 PM - ftpuser (127.0.0.1)> LIST *.zip0 (000021) 11/27/2006 16:20:44 PM - ftpuser (127.0.0.1)> 150 Connection accepted (000021) 11/27/2006 16:20:44 PM - ftpuser (127.0.0.1)> SSL connection for data connection established (000021) 11/27/2006 16:20:44 PM - ftpuser (127.0.0.1)> 226 Transfer OK (000021) 11/27/2006 16:20:45 PM - ftpuser (127.0.0.1)> PASV (000021) 11/27/2006 16:20:45 PM - ftpuser (127.0.0.1)> 227 Entering Passive Mode (127,0,0,1,117,49) (000021) 11/27/2006 16:20:45 PM - ftpuser (127.0.0.1)> LIST *.zip0 (000021) 11/27/2006 16:20:45 PM - ftpuser (127.0.0.1)> 150 Connection accepted (000021) 11/27/2006 16:20:45 PM - ftpuser (127.0.0.1)> SSL connection for data connection established (000021) 11/27/2006 16:20:45 PM - ftpuser (127.0.0.1)> 226 Transfer OK (000021) 11/27/2006 16:20:46 PM - ftpuser (127.0.0.1)> PASV (000021) 11/27/2006 16:20:46 PM - ftpuser (127.0.0.1)> 227 Entering Passive Mode (127,0,0,1,117,50) (000021) 11/27/2006 16:20:46 PM - ftpuser (127.0.0.1)> LIST *.zip0 (000021) 11/27/2006 16:20:46 PM - ftpuser (127.0.0.1)> 150 Connection accepted (000021) 11/27/2006 16:20:46 PM - ftpuser (127.0.0.1)> 226 Transfer OK Several “good†ones at the beginning and a “bad†one at the end. On the “good†attempts, between the “150 Connection accepted†and “226 Transfer OK†there’s a “227 Entering Passive Mode†line, which is missing on the “bad†one. |
||||||
#1197 | Year bug | Bug report | normal | FileZilla Server | |||
Description |
As searching in summary and resulting in 0 matches concerning this bug, I'm going to postit: under windows server 2003 and Filezilla server v 0.9.20 all downloaded files appears with CurrentYear-1 in datetime file properties in ALL windows OSes It's like FileZilla decrements the year number in one?? |
||||||
#1199 | Error displaying file list for folders with lots of files | Bug report | normal | FileZilla Server | |||
Description |
I've a folder with files named after iso-dates (yyyy-mm-dd). Filezilla server seems to serve well for listing the first 240 (around that) files. Then it never finish the parts after that. |
||||||
#1204 | Cannot open folder with about 1200 files | Bug report | normal | FileZilla Server | |||
Description |
(000011) 12/13/2006 18:58:30 PM - jkealey (MY_IP)> CWD inventory (000011) 12/13/2006 18:58:30 PM - jkealey (MY_IP)> 250 CWD successful. "/Inetpub/wwwroot/websitename.com/web/images/inventory" is current directory. (000011) 12/13/2006 18:58:30 PM - jkealey (MY_IP)> PWD (000011) 12/13/2006 18:58:30 PM - jkealey (MY_IP)> 257 "/Inetpub/wwwroot/websitename.com/web/images/inventory" is current directory. (000011) 12/13/2006 18:58:30 PM - jkealey (MY_IP)> TYPE A (000011) 12/13/2006 18:58:30 PM - jkealey (MY_IP)> 200 Type set to A (000011) 12/13/2006 18:58:30 PM - jkealey (MY_IP)> PASV (000011) 12/13/2006 18:58:30 PM - jkealey (MY_IP)> 227 Entering Passive Mode (SE,RV,ER,IP,15,201) (000011) 12/13/2006 18:58:30 PM - jkealey (MY_IP)> LIST (000011) 12/13/2006 18:58:30 PM - jkealey (MY_IP)> 150 Connection accepted (000011) 12/13/2006 18:58:33 PM - jkealey (MY_IP)> 226 Transfer OK (000011) 12/13/2006 18:59:07 PM - jkealey (MY_IP)> disconnected. The last disconnected is the filezilla client that disconnects after a timeout. Other clients like IE stay connected. |
||||||
#1208 | ip script web page don't work! | Bug report | normal | FileZilla Server | |||
Description |
Hi,
Summary: A. fix the script page.
|
||||||
#1213 | Can't retrive Dynamic IP | Bug report | normal | FileZilla Server | |||
Description |
Hi I'm using FileZilla 0.9.19 Beta and in the Passive Mode Settings the link "http://filezilla.sourceforge.net/misc/ip.php" is not retriving the external IP, seeing that i have a dynamic IP i need this option, the SSL FTP only works from outside the local network after i manually put the external IP in the field "Use the Folloing IP". What am i doing wrong? Is the link correct? Thanks Jorge Maia |
||||||
#1214 | 0.9.22 still doesn't do PASV behind a firewall properly | Bug report | normal | FileZilla Server | |||
Description |
I've seen similar bugs opened and closed in this bug tracking system, usually blaming the router, but I think that this is still a problem in the latest version of Filezilla Server 0.9.22. Here's what I did to demonstrate this. Inside a router firewall, I set up two servers, one WinXP with Filezilla 0.9.22. The other was a CentOS server running vsftpd. The router was set up to pass ports 20,21 as well as ports 1024-1033, with the two FTP servers configured accordingly. Outside the firewall, I had two Unix servers, one running CentOS, and the other running FreeBSD. The FTP client on the CentOS system speaks PASV mode only. When the router was set to point to the CentOS system behind my firewall, then things worked -- the 227 response provided my public IP (of the router), and two port numbers, which when multiplied together, provided something in the specified range of 1024-1033. However, when the router was redirected with the same rules to point to the Filezilla server (differen LAN IP only), then I could log in, but I could not execute an 'ls'. Looking at the Filezilla server log, a correct 227 response to the PASV mode command was entered, but apparently never properly received by the CentOS FTP client. So it hung until the connection timed out. On the other hand, the FTP client of the FreeBSD server outside the firewall speaks EPSV, which seems to work fine with both the CentOS and Filezilla servers behind my firewalls. With EPSV, the port number to use is transmitted premultiplied together. If the router were to blame, it would not have handled the CentOS system behind the firewall properly either, would it? A log file of the CentOS client trying to connect to the two server is attached. |
||||||
#1217 | Permission denied bug | Bug report | normal | FileZilla Server | |||
Description |
FileZilla_Server-0_9_22.exe i want append file, when empty file exist locally. error transfer occur, when permission set of R+ W+ A+ D- when i change permission to D+, transmission error disappears log begin(000002) 12.01.2007 11:39:03 - xxxxxx (10.35.xxx.xxx)> 230 Logged on (000002) 12.01.2007 11:39:04 - xxxxxx (10.35.xxx.xxx)> PWD (000002) 12.01.2007 11:39:04 - xxxxxx (10.35.xxx.xxx)> 257 "/" is current directory. (000002) 12.01.2007 11:39:04 - xxxxxx (10.35.xxx.xxx)> PORT 10,35,194,43,112,102 (000002) 12.01.2007 11:39:04 - xxxxxx (10.35.xxx.xxx)> 200 Port command successful (000002) 12.01.2007 11:39:04 - xxxxxx (10.35.xxx.xxx)> TYPE I (000002) 12.01.2007 11:39:04 - xxxxxx (10.35.xxx.xxx)> 200 Type set to I (000002) 12.01.2007 11:39:04 - xxxxxx (10.35.xxx.xxx)> SIZE Abc-(10.35.xxx.xxx)_2007.01.12-00.10.00.7z (000002) 12.01.2007 11:39:04 - xxxxxx (10.35.xxx.xxx)> 213 0 (000002) 12.01.2007 11:39:04 - xxxxxx (10.35.xxx.xxx)> STOR Abc-(10.35.xxx.xxx)_2007.01.12-00.10.00.7z (000002) 12.01.2007 11:39:04 - xxxxxx (10.35.xxx.xxx)> 550 Permission denied (000002) 12.01.2007 11:39:04 - xxxxxx (10.35.xxx.xxx)> disconnected. log endFileZilla Server.xml begin[==skip==] <Group Name="pal"> <Option Name="Bypass server userlimit">0</Option> <Option Name="User Limit">0</Option> <Option Name="IP Limit">0</Option> <Option Name="Enabled">1</Option> <Option Name="Comments"/> <Option Name="ForceSsl">0</Option> <IpFilter> <Disallowed/> <Allowed/> </IpFilter> <Permissions> <Permission Dir="C:\Pal"> <Option Name="FileRead">1</Option> <Option Name="FileWrite">1</Option> <!-- bug line begin --> <Option Name="FileDelete">0</Option> <!-- bug line end --> <Option Name="FileAppend">1</Option> <Option Name="DirCreate">0</Option> <Option Name="DirDelete">0</Option> <Option Name="DirList">1</Option> <Option Name="DirSubdirs">1</Option> <Option Name="IsHome">1</Option> <Option Name="AutoCreate">0</Option> </Permission> </Permissions> <SpeedLimits DlType="1" DlLimit="10" ServerDlLimitBypass="0" UlType="1" UlLimit="10" ServerUlLimitBypass="0"> <Download/> <Upload/> </SpeedLimits> [==skip==] FileZilla Server.xml begin |
||||||
#1221 | http://ip.filezilla-project.org/ip.php returns 127.0.0.1 | Bug report | normal | FileZilla Server | |||
Description |
http://ip.filezilla-project.org/ip.php returns 127.0.0.1 |
||||||
#1224 | "FileZilla Server.exe" crashes during Windows shutdown | Bug report | normal | FileZilla Server | outdated | ||
Description |
Hi, I'm using FileZilla Server 0.9.22 on WinXP Pro workstations and the service "FileZilla Server.exe" crashes during Windows shutdown with message "Instruction <xxxxxxxx> use memory address <yyyyyyyy>. Can't be "Read". I get this error on several machines, each equiped with "McAfee VirusScan Enterprise v8" (I'm not sure it's caused by McAfee but it's the only software in common) |
||||||
#1229 | UTF8 on NT4(English) isn't work correctly | Bug report | normal | FileZilla Server | |||
Description |
Any filename with non-English characters in filename can't be downloaded from FileZilla Server on NT4 (english). On WinXP (russian) all is OK. Log from NT4: (000111) 09.02.07 19:31:18 - nitr0 (192.168.192.156)> RETR РСћРВµРÐРѓРЂ.txt (000111) 09.02.07 19:31:18 - nitr0 (192.168.192.156)> 550 File not found Log from XP: (000004) 09.02.2007 19:37:28 - anonymous (192.168.192.156)> RETR ТеÑÑ‚.txt (000004) 09.02.2007 19:37:28 - anonymous (192.168.192.156)> 150 Opening data channel for file transfer. Why on NT4 CP1251 filename is converted to UTF-8 normally, but UTF-8 filename can't be converted to CP-1251? |
||||||
#1235 | Log file captures logs meant for next day | Bug report | normal | FileZilla Server | |||
Description |
When Filezilla generates the log file, the cutoff time incorrectly follows the UTC instead of the machine's local time. Hence the logs supposedly for next day's is captured in the log file for that day. i.e. fzs-2007-02-12.log 1456KB Text Document 2/13/2007 7:59AM wherein the last column is the last update date/time of the file. Time is at +8 GMT. In line 133 of http://filezilla.cvs.sourceforge.net/filezilla/FileZilla%20Server/source/FileLogger.cpp?view=markup "getsystemtime" should be "GetLocalTime" Please refer to forum thread http://filezilla.sourceforge.net/forum/viewtopic.php?p=11277#11277 |
||||||
#1244 | v0.9.23 beta, Interface can't connect to Server | Bug report | normal | FileZilla Server | |||
Description |
When start Server manually is selected, the Interface can't connect to the Server until the Server has been started, and the Interface has connected while the Server is online. After this the Interface is able to connect to the Server when it is offline. However this makes remote administration impossible, if you want to be able to start and stop the Server manually. |
||||||
#1249 | special characters | Bug report | normal | FileZilla Server | |||
Description |
Hi, I use Filezilla server 0.9.23 beta on Win2000 server SP4. I have problem with "french" characters, I don't know the words to explain so here is an example. here is a sample of the filezilla log. (000018) 2007-03-21 17:55:04 - mrouillard (10.0.0.12)> CWD /Bases de données (000018) 2007-03-21 17:55:04 - mrouillard (10.0.0.12)> 250 CWD successful. "/Bases de données" is current directory. (000018) 2007-03-21 17:55:04 - mrouillard (10.0.0.12)> PWD (000018) 2007-03-21 17:55:04 - mrouillard (10.0.0.12)> 257 "/Bases de données" is current directory. and this is what I see in my ftp clients, for the current directory. /Bases de données Is there a way to arrange that? I have tried with CuteFtp and Directory Opus, and Ie7. Thanks. |
||||||
#1251 | MFMT does not accept time with hours == 0 | Bug report | normal | FileZilla Server | |||
Description |
FileZilla 0.9.23: "MFMT 20070319003137 file.dat" fails with "invalid date" message. It appears, that it does not accept 00:31:37 as a valid time - if I replace the 00 by 01, for instance, it works. "MDTM file.dat", on the other hand, returns 20070319003137 if the file date has been set by other means (copying by explorer :-)). Thanks |
||||||
#1253 | incomplete file listing | Bug report | normal | FileZilla Server | outdated | ||
Description |
I've found big prbs in filezilla server v0.9.23b(win) with the file listing. Filezilla fails to list all directories from a directory. This prb appears only when users access my server from internet. From the intranet this prb doesn't appear. File listing becomes incomplete when in a directory there are more than 150 directories. |
||||||
#1260 | aliases not working with some directory names | Bug report | low | FileZilla Server | |||
Description |
I run the latest version of filezilla server in windows xp pro and have the following problem: I have set E:\[mp3]\ as my home directory and added another directory D:\[movies]\ with the alias E:\[mp3]\movies ..and the movies alias doesn't show up. I have tried some different solutions and it seems like the "and" -signs are the cause of the trouble. |
||||||
#1262 | PORT Command Octal IP | Bug report | normal | FileZilla Server | |||
Description |
Hello, i have posted a Feature Requst (1714025)... After looking trough the Sourcecode i found following: ControllSocket.cpp #ifdef _UNICODE
#else
#endif
When the IP is octal then res are not INADDR_NONE. I mean this is a bug... Greetings Tobias |
||||||
#1263 | Port COMMAND IP Parsing | Bug report | normal | FileZilla Server | |||
Description |
Re, When a Client (IP 172.17.6.201) connect to Filezilla and send the command: "PORT 172,017,006,201,11,94" Then Filzilla Server trys to connect to 172.15.6.201. I have here a TCP Dump (dumped with wireshark). I attached the dump (exported as txt) There you can see, the Request: PORT 172,017,006,201,57,232 and then trys filezilla 172.17.6.50 172.15.6.201 TCP 20 > 14824 [SYN] Seq=0 Len=0 MSS=1460 That is a bug. |
||||||
#1269 | Passive mode PORT doesn't work | Bug report | normal | FileZilla Server | |||
Description |
When connecting in Passive Mode AND using SSL/TLC connection (normal ftp mode works) AND with selected option 'Use custom port range', the server sends: 227 Entering Passive Mode (ip,ip,ip,ip,port1,port2) but the it doesn't listen on the port specified here. So the client can't connect. Server version used: 0.9.23, for Windows. |
||||||
#1271 | Cannot do a directory list | Bug report | normal | FileZilla Server | |||
Description |
We cannot get a directory from a server running filezilla that is not under our control. The outside owner of the server sent us this log. What is the problem with this. We get the same results using nlist or nlst. 000045) 6/19/2007 15:15:41 PM - (not logged in) (216.249.132.11)> Connected, sending welcome message... (000045) 6/19/2007 15:15:41 PM - (not logged in) (216.249.132.11)> 220 %SIS (000045) 6/19/2007 15:15:41 PM - (not logged in) (216.249.132.11)> SSL connection established (000045) 6/19/2007 15:15:41 PM - (not logged in) (216.249.132.11)> USER kyvuksu (000045) 6/19/2007 15:15:41 PM - (not logged in) (216.249.132.11)> 331 Password required for kyvuksu (000045) 6/19/2007 15:15:42 PM - (not logged in) (216.249.132.11)> PASS (000045) 6/19/2007 15:15:42 PM - kyvuksu (216.249.132.11)> 230 Logged on (000045) 6/19/2007 15:15:42 PM - kyvuksu (216.249.132.11)> PROT P (000045) 6/19/2007 15:15:42 PM - kyvuksu (216.249.132.11)> 200 Protection level set to P (000045) 6/19/2007 15:15:42 PM - kyvuksu (216.249.132.11)> PASV (000045) 6/19/2007 15:15:42 PM - kyvuksu (216.249.132.11)> 227 Entering Passive Mode (207,49,65,62,195,86) (000045) 6/19/2007 15:15:43 PM - kyvuksu (216.249.132.11)> SSL connection for data connection established (000045) 6/19/2007 15:15:43 PM - kyvuksu (216.249.132.11)> LIST (000045) 6/19/2007 15:15:43 PM - kyvuksu (216.249.132.11)> 150 Connection accepted (000045) 6/19/2007 15:15:43 PM - kyvuksu (216.249.132.11)> Data connection SSL warning: SSL3 alert write: fatal: bad record mac (000045) 6/19/2007 15:15:43 PM - kyvuksu (216.249.132.11)> QUIT |
||||||
#1280 | MD5sum incorrect | Bug report | normal | FileZilla Server | |||
Description |
The md5sum for the file FileZilla_Server-0_9_23.exe as mentioned in FileZilla_Server-0_9_23.exe.md5 is incorrect (Two download locations gave a different but identical md5sum). |
||||||
#1281 | Typo on FileZilla Server Security Settings options Page | Bug report | low | FileZilla Server | |||
Description |
Has the word bandwich instead of bandwidth. |