Debian Codegraph @

README

raw
1 This is linux-ftpd-0.17 for Linux, a port of the OpenBSD ftp daemon.
2
3 This package updates linux-ftpd-0.16.
4
5 If you're reading this off a CD, go right away and check the net
6 archives for later versions and security fixes. As of this writing the
7 home site for NetKit is
8 ftp://ftp.uk.linux.org/pub/linux/Networking/netkit
9
10 Contents:
11 ftpd Daemon for the ftp protocol.
12
13 Requires:
14 Working compiler, libc, and kernel.
15 Supports shadow passwords. Does not (yet) support PAM.
16
17 Security:
18 This version contains vital fixes for a remotely exploitable
19 hole relating to printf format string processing.
20 linux-ftpd-0.16 and earlier should not be used.
21
22 Restrictions:
23 This version does not put ftp users in utmp; the utmp code is
24 #if'd out. This means the -U option does not work.
25
26 Keep in mind that the man page has not been completely edited
27 for Linux and may refer to a few BSDisms.
28
29 Port information:
30 The source was retrieved from ftp.openbsd.org on
31 Thu Jul 15 19:38:16 EDT 1999
32
33 including the files
34 extern.h ftpcmd.y ftpd.8 ftpd.c
35 logutmp.c logwtmp.c pathnames.h popen.c
36
37 These came from src/libexec/ftpd.
38
39 The support files came from various sources, including
40 OpenBSD's libc, NetKit 0.09, and sendmail 8.7.4. (8.7.4
41 because it was handy, not for any particular reason.) Others
42 were written for this port.
43
44 Installation:
45 Do "./configure --help" and decide what options you want. The
46 defaults should be suitable for most Linux systems. Then run
47 the configure script.
48
49 Do "make" to compile.
50 Then (as root) do "make install".
51
52 Save a backup copy of any mission-critical program in case the
53 new one doesn't work, and so forth. We warned you.
54
55 If you get gcc warnings from files in /usr/include, they are
56 due to problems in your libc, not netkit. (You may only see
57 them when compiling netkit because netkit turns on a lot of
58 compiler warnings.)
59
60 DEC CC:
61 The DEC compiler for the Alpha is now freely available. This
62 is a much better compiler with gcc, that is, it generates much
63 better code. If you have the DEC compiler, you can explicitly
64 use the DEC compiler instead of gcc by configuring like this:
65
66 ./configure --with-c-compiler=ccc
67
68 It is known to generate spurious warnings on some files. Also,
69 some headers from some versions of glibc confuse it; that may
70 prevent netkit from working. Other problems should be reported
71 as bugs.
72
73 Bugs:
74 Send bug reports and whatnot to the netkit bug address, not to
75 OpenBSD, as the OpenBSD organization doesn't have anything
76 official to do with this port. Things will be forwarded if
77 necessary.
78
79 Please make sure the header files in /usr/include match the
80 libc version installed in /lib and /usr/lib. If you have weird
81 problems this is the most likely culprit.
82
83 Also, before reporting a bug, be sure you're working with the
84 latest version.
85
86 If something doesn't compile for you, fix it and send diffs.
87 If you can't, send the compiler's error output.
88
89 If it compiles but doesn't work, send as complete a bug report as
90 you can. Patches and fixes are welcome, as long as you describe
91 adequately what they're supposed to fix. Please, one patch per
92 distinct fix. Please do NOT send the whole archive back or
93 reindent the source.
94
95 Be sure to send all correspondence in e-mail to the netkit address.
96 Postings to netnews or mailing lists will not be seen due to the
97 enormous volume. Also, anything that doesn't get filed in the bug
98 database is quite likely to end up forgotten.
99
100 Please don't report known bugs (see the BUGS file(s)) unless you
101 are including fixes. :-)
102
103 Mail should be sent to: [email protected]
104
105
106 Early in April 2000, a hacker broke into the machine that was hosting
107 the netkit bug database for me and trashed it. Unfortunately, it seems
108 backups hadn't gotten done for a while, so three months of mail (since
109 mid-January) was lost. So, if you sent something and didn't hear back,
110 or you sent something, heard back, but the changes failed to appear in
111 this release (unlikely but possible) - please resend.
112
113 Please see http://www.hcs.harvard.edu/~dholland/computers/netkit.html
114 if you are curious why it was so long between the 0.10 and 0.16 releases.
115
116 Future plans for netkit maintenance are still up in the air, but in the
117 meantime new releases will still appear from time to time. I don't have
118 a whole lot of cycles to spare to work on netkit, so things are likely
119 to continue to be fairly slow.
120
121 David A. Holland
122 23 July 2000