"Fossies" - the Fresh Open Source Software Archive 
As a special service "Fossies" has tried to format the requested text file into HTML format (style:
standard) with prefixed line numbers.
Alternatively you can here
view or
download the uninterpreted source code file.
1 MOD_FTP STATUS: -*-text-*-
2 Last modified at [$Date: 2009-09-28 22:04:37 -0500 (Mon, 28 Sep 2009) $]
3
4 The current version of this file can be found at:
5
6 * http://svn.apache.org/repos/asf/httpd/mod_ftp/trunk/STATUS
7
8 Consult the following STATUS files for information on related projects:
9
10 * http://svn.apache.org/repos/asf/httpd/httpd/trunk/STATUS
11 * http://svn.apache.org/repos/asf/apr/apr/trunk/STATUS
12
13 Release history:
14 [NOTE that x.{odd}.z versions are strictly Alpha/Beta releases,
15 while x.{even}.z versions are Stable/GA releases.]
16
17 0.9.7 : in development
18 0.9.6 : tagged September 28, 2009
19 0.9.5 : not released
20 0.9.4 : not released
21 0.9.3 : not released
22 0.9.2 : released as beta June 27, 2008
23 0.9.1 : not released
24 0.9.0 : not released
25
26 Contributors looking for a mission:
27
28 * Just do an egrep on "TODO" or "XXX" in the source.
29
30 * Review the bug database at: http://issues.apache.org/bugzilla/
31
32 * Review the "PatchAvailable" bugs in the bug database:
33
34 https://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&component=mod_ftp&keywords=PatchAvailable
35
36 After testing, you can append a comment saying "Reviewed and tested".
37
38 * Open bugs in the bug database
39
40 https://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&component=mod_ftp
41
42
43 RELEASE SHOWSTOPPERS:
44
45
46
47 CURRENT RELEASE NOTES:
48
49 * EPSV and EPRT need real world testing for different routing and DMZ
50 cases and validating a range of IPv6-enabled clients' interop.
51 Note many IPv4-only NAT routers appear to ignore EPRT commands,
52 even as they would fix up NAT addresses from PORT commands.
53
54 * Extra attention should be paid to PORT and EPRT connections, especially
55 when assigned low numbered ports, e.g. FTPActiveRange 20
56
57
58 CURRENT VOTES:
59
60
61
62 REALLY NICE TO WRAP THESE UP:
63
64 * For in-tree builds, extending config_vars.mk with our local
65 [exp_]ftpdocsdir and installing that tree.
66
67 * For in-tree builds, expanding @@FTPPort@@ / @exp_ftpdocsdir@
68 and installing conf/extra/ftpd.conf.
69
70 * Fix SIZE implementation to inject the Content Length filter and
71 report the true size, required for proper REST support. Also
72 ensure REST point accounts for A/I TYPE in-force.
73
74 * Grant LIST, NLST richer parsing of -opts, with --<SP> designating
75 no-opts (to conform to RFC2640).
76
77 * dot-files (E.g. ".filename") are always shown, while "." this-dir and
78 ".." (parent directory) are never shown. Additional LIST/NLST options
79 are necessary before these are hidden by default, which implies a
80 fairly significant refactoring.
81
82 * Implement LANG command and feature as our Accept-Language bluff;
83 "Internationalization of the File Transfer Protocol", Curtin
84 http://www.ietf.org/rfc/rfc2640.txt
85
86 * Implement RFC2228 ADAT and AUTH GSSAPI commands Appendix I and/or
87 AUTH KERBEROS_V4 from Appendix II as desired, but ideally as
88 loadable FTP extension modules due to the library dependencies,
89 and be sure to evaluate license compatibility issues.
90 "FTP Security Extensions", Horowitz, Lunt
91 http://www.ietf.org/rfc/rfc2228.txt
92
93 * Implement additional features, MLST and MLSD, but mind the errata.
94 "Extensions to FTP", Hethmon
95 http://www.ietf.org/rfc/rfc3659.txt
96 http://www.rfc-editor.org/errata_search.php?rfc=3659
97
98 * Implement RFC1639, if anyone is so motivated.
99 "FTP Operation Over Big Address Records (FOOBAR)", Piscitello
100 http://www.rfc-editor.org/rfc/rfc1639.txt
101
102 * In httpd 2.3-dev and later, it's no longer possible to process
103 Require dir-name
104 which meant that mod_ftp auth required that the logged in user match
105 the name of the directory in which the Require was placed. This
106 should be added as a seperate authz provider, or refactored to the
107 new auth syntax (or simply dropped?)
108
109
110 REFERENCES:
111
112 * "FILE TRANSFER PROTOCOL (FTP)", Postel, Reynolds
113 http://www.ietf.org/rfc/rfc959.txt
114
115 * "TELNET PROTOCOL SPECIFICATION", Postel, Reynolds
116 http://www.ietf.org/rfc/rfc854.txt
117
118 * "Requirements for Internet Hosts -- Application and Support", Braden
119 http://www.ietf.org/rfc/rfc1123.txt
120
121 * "FTP Operation Over Big Address Records (FOOBAR)", Piscitello
122 http://www.rfc-editor.org/rfc/rfc1639.txt
123
124 * "FTP Security Extensions", Horowitz, Lunt
125 http://www.ietf.org/rfc/rfc2228.txt
126
127 * "FTP Extensions for IPv6 and NATs", Allman, Ostermann, Metz
128 http://www.ietf.org/rfc/rfc2428.txt
129
130 * "Extensions to FTP", Hethmon
131 http://www.ietf.org/rfc/rfc3659.txt
132 http://www.rfc-editor.org/errata_search.php?rfc=3659
133
134 * "Securing FTP with TLS", Ford-Hutchinson
135 http://www.ietf.org/rfc/rfc4217.txt
136