Debian Codegraph @

README

raw
1 This is bsd-finger-0.17 for Linux.
2
3 This package updates bsd-finger-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 finger Program for printing user information
12 fingerd Daemon for remote finger access
13
14 Requires:
15 Working compiler, libc, and kernel.
16
17 Security:
18 bsd-finger-0.17 contains no new security fixes.
19
20 bsd-finger-0.16 fixes some possible denial of service attacks
21 against fingerd.
22
23 bsd-finger-0.10 fixed a denial of service situation where
24 users' .plan or .project files are named pipes.
25
26 The NetKit-0.09 and earlier versions of this code fixed a
27 number of now well-known security problems. Please don't use
28 older versions.
29
30 Note:
31 If you are using the finger daemon from this package with a
32 custom finger client, rather than the finger client in this
33 package, you will need to update your client to send carriage
34 returns (CR, or '\r' in C) before line feeds (LF, or '\n' in
35 C) if the finger client's standard output is a socket.
36
37 This is because as of bsd-finger-0.15, finger probes this
38 condition and sends CRs itself instead of expecting fingerd
39 to make an extra copy of all the data through a pipe just to
40 add CRs in.
41
42 Ignoring this circumstance and always sending LF instead of
43 CR/LF will in most cases work, but is not RFC-compliant.
44
45 Installation:
46 Do "./configure --help" and decide what options you want. The
47 defaults should be suitable for most Linux systems. Then run
48 the configure script.
49
50 Do "make" to compile.
51 Then (as root) do "make install".
52
53 Save a backup copy of any mission-critical program in case the
54 new one doesn't work, and so forth. We warned you.
55
56 If you get gcc warnings from files in /usr/include, they are
57 due to problems in your libc, not netkit. (You may only see
58 them when compiling netkit because netkit turns on a lot of
59 compiler warnings.)
60
61 DEC CC:
62 The DEC compiler for the Alpha is now freely available. This
63 is a much better compiler with gcc, that is, it generates much
64 better code. If you have the DEC compiler, you can explicitly
65 use the DEC compiler instead of gcc by configuring like this:
66
67 ./configure --with-c-compiler=ccc
68
69 It is known to generate spurious warnings on some files. Also,
70 some headers from some versions of glibc confuse it; that may
71 prevent netkit from working. Other problems should be reported
72 as bugs.
73
74 Bugs:
75 Please make sure the header files in /usr/include match the
76 libc version installed in /lib and /usr/lib. If you have weird
77 problems this is the most likely culprit.
78
79 Also, before reporting a bug, be sure you're working with the
80 latest version.
81
82 If something doesn't compile for you, fix it and send diffs.
83 If you can't, send the compiler's error output.
84
85 If it compiles but doesn't work, send as complete a bug report as
86 you can. Patches and fixes are welcome, as long as you describe
87 adequately what they're supposed to fix. Please, one patch per
88 distinct fix. Please do NOT send the whole archive back or
89 reindent the source.
90
91 Be sure to send all correspondence in e-mail to the netkit address.
92 Postings to netnews or mailing lists will not be seen due to the
93 enormous volume. Also, anything that doesn't get filed in the bug
94 database is quite likely to end up forgotten.
95
96 Please don't report known bugs (see the BUGS file(s)) unless you
97 are including fixes. :-)
98
99 Mail should be sent to: [email protected]
100
101
102 Early in April 2000, a hacker broke into the machine that was hosting
103 the netkit bug database for me and trashed it. Unfortunately, it seems
104 backups hadn't gotten done for a while, so three months of mail (since
105 mid-January) was lost. So, if you sent something and didn't hear back,
106 or you sent something, heard back, but the changes failed to appear in
107 this release (unlikely but possible) - please resend.
108
109 Please see http://www.hcs.harvard.edu/~dholland/computers/netkit.html
110 if you are curious why it was so long between the 0.10 and 0.16 releases.
111
112 Future plans for netkit maintenance are still up in the air, but in the
113 meantime new releases will still appear from time to time. I don't have
114 a whole lot of cycles to spare to work on netkit, so things are likely
115 to continue to be fairly slow.
116
117 David A. Holland
118 23 July 2000