Hide Forgot
Description of problem: while researching a Problem in wordpress i found a Problem in proftpd. Wordpress tries to send at some point a "TYPE A" Command to a ftp Server, which after RFC 959 Switches to ASCII. While proftpd accepts "type ascii" without Problems as command on the ftp console, it delivers for a "type a" command a result as "a: unknown mode" while rfc 959 (http://www.ietf.org/rfc/rfc959.txt, page 28) requires this to work. Version-Release number of selected component (if applicable): proftpd-1.3.4d-4.fc19.src.rpm How reproducible: Setup proftpd, Login into a valid account Steps to Reproduce: 1. ftp localhost 2. authenticate (--> even anymouse) 3. type a --> results in a: unkown mode Actual results: admin@production ~]$ ftp localhost Trying ::1... Connected to localhost (::1). 220 FTP Server ready. Name (localhost:admin): test 331 Password required for test Password: 230 User test logged in Remote system type is UNIX. Using binary mode to transfer files. ftp> type a a: unknown mode ftp> Expected results: Same result as ftp> type ascii 200 Type set to A Additional info:
The problem here is the client, which is generating the "unknown mode" response itself and not actually passing the command to the server. You can verify this for yourself by running proftpd in debug mode so that you can see the commands it is processing, and/or using the same client with another server such as vsftpd, where you'll see the same behaviour.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.