| | 1 | pidentd |
| | 2 | |
| | 3 | ("Peter's Ident Daemon" or is it "Portable Ident Daemon"?) |
| | 4 | |
| | 5 | Peter Eriksson <pen@lysator.liu.se> |
| | 6 | |
| | 7 | |
| | 8 | This program is released into the public domain and can be used by |
| | 9 | anyone who wants to. Vendors may include it into their distributions |
| | 10 | if they want to without any restrictions. (Although it would be nice |
| | 11 | to be notified by email if someone decides to do that, and/or a note |
| | 12 | somewhere about who wrote this program. Like in the man-page or so.. :-) |
| | 13 | |
| | 14 | This is a program that implements the RFC1413 identification server. It |
| | 15 | was very much inspired by Dan Bernstein's original 'authd' (but unlike |
| | 16 | that program doesn't use 'netstat' to get some of the information) It |
| | 17 | uses the kernel information directly. (And is due to that fact a lot |
| | 18 | faster). Dan has now written another version of the 'authd' daemon that |
| | 19 | uses his 'kstuff' to read the kernel information. Unlike that daemon, |
| | 20 | this will use only normally available kernel access functions (and is due |
| | 21 | to that more limited in the different machines it support). Please note |
| | 22 | that this daemon used to be called pauthd but has changed name to better |
| | 23 | reflect what it does (and to conform to the new RFC). |
| | 24 | |
| | 25 | This daemon has been tested on the following machines/OS (please report |
| | 26 | to me if you've tested a newer version, or if your machine/OS isn't among |
| | 27 | the ones below): |
| | 28 | |
| | 29 | Machine Operating System Pidentd version |
| | 30 | ---------------------- ---------------------- -------------------------- |
| | 31 | Sequent Balance Dynix 3.0.14 2.1beta.12 |
| | 32 | Sequent Symmetry Dynix 3.1.2 2.1beta.3 |
| | 33 | Sun 3/50 SunOS 3.5 2.1beta.8.1 (3) |
| | 34 | Sun 386i SunOS 4.0.2 1.9beta |
| | 35 | Sun 2/120 SunOS 4.0.3 2.1beta.10 |
| | 36 | Sun 3/280 SunOS 4.1.1 2.1beta.12 |
| | 37 | Sun 4/380 SunOS 4.1.3 2.1beta.12 |
| | 38 | Sun SS1/41 SunOS 5.1 2.1beta.11 |
| | 39 | HP 9000/375 HP-UX 7.0 2.1beta.10.1 (1) |
| | 40 | HP 9000/300 HP-UX 8.0 2.1beta.12 |
| | 41 | HP 9000/340 HP-UX 8.0 2.1beta.10.1 |
| | 42 | HP 9000/360 HP-UX 8.0 2.1beta.10.1 |
| | 43 | HP 9000/710 HP-UX 8.07 2.1beta.10.1 |
| | 44 | HP 9000/720 HP-UX 8.07 2.1beta.10.1 |
| | 45 | HP 9000/715 HP-UX 9.0 2.1beta.9.1 |
| | 46 | HP 9000/827 HP-UX 8.02 2.1beta.8.1 |
| | 47 | HP 9000/834 HP-UX 7.0 2.0beta.4 |
| | 48 | HP 9000/835 HP-UX 8.00 2.1beta.10.1 |
| | 49 | MIPS RISC/OS 4.5x 2.1beta.8.1 |
| | 50 | DECstation 2100 Ultrix 4.2-96 2.1beta.2 (2) |
| | 51 | DECstation 5000/133 Ultrix 4.2 2.1beta.9.1 (2) [?] |
| | 52 | DEC VAXstation 2000 Ultrix-32 3.1 2.1beta.12 (2) [?] |
| | 53 | DEC VAX vs3520 Ultrix 3.0 2.1beta.9.1 (2) [?] |
| | 54 | DEC VAX 11/780 4.3BSD Reno 2.1beta.12 (2) |
| | 55 | i486-PC UHC SVR4 2.0 2.0beta.4 (2) |
| | 56 | i486-PC Dell SVR4 2.2 2.0beta.4 (2) |
| | 57 | i486-PC ESIX SVR4 4.0.4 2.1beta.2 (2) |
| | 58 | i486-PC 386BSD 0.1 2.1beta.3 (2) |
| | 59 | Cray UNICOS 6.0.12 2.1beta.7 |
| | 60 | NeXT NeXTSTEP 2.1 2.1beta.9.1 (3) |
| | 61 | NeXT NeXTSTEP 3.0 2.1beta.9.1 (3) |
| | 62 | Pyramid 90x dualPort OSx 4.1 2.1beta.12 |
| | 63 | Silicon Graphics IRIX 4 2.1beta.10 |
| | 64 | |
| | 65 | Notes: |
| | 66 | 1) HP-UX 7.0 doesn't support running streams based services from |
| | 67 | Inetd with the "wait" option (and the "-w" flag to Pidentd). |
| | 68 | |
| | 69 | It also has problems with starting stuff as user "sys" from Inetd. |
| | 70 | (It doesn't correctly set the group id to "sys") so I suggest you |
| | 71 | either starts it as user "root" and use the "-u" and "-g" flags |
| | 72 | to setuid and setgid itself to user "sys", group "sys", or do a |
| | 73 | 'chgrp sys in.identd' and then a 'chmod g+s in.identd' and start |
| | 74 | it as user "sys" from Inetd. |
| | 75 | |
| | 76 | 2) These systems also doesn't support running streams based |
| | 77 | services from Inetd with the "wait" option. |
| | 78 | |
| | 79 | 3) See notes in the READMEs/README.<machine-type> specific files. |
| | 80 | |
| | 81 | |
| | 82 | Please let me know if you find any bugs, or have ported it to other |
| | 83 | machines (and care to share the changes with me and the world!). |
| | 84 | |
| | 85 | See the manual page for information about the various command line |
| | 86 | options that are available. |
| | 87 | |
| | 88 | NOTE: One should NOT use the -d option when using it for normal use! |
| | 89 | |
| | 90 | If you intend to create or modify daemons that use the IDENT protocol |
| | 91 | then you may wish to get the "libident" library that contains some |
| | 92 | functions to implement the client side of this protocol. It is available |
| | 93 | as "libident-*.tar.Z" in "pub/ident/libs" at "ftp.lysator.liu.se". |
| | 94 | |
| | 95 | There is a mailing list for users of the IDENT(RFC1413)/TAP protocol called |
| | 96 | 'ident-users@lysator.liu.se' that you may want to consider joining. |
| | 97 | Send mail to the address 'ident-users-request@lysator.liu.se' to |
| | 98 | join it. This list is intended for generic discussions on using this |
| | 99 | protocol and it's associated tools. |
| | 100 | |
| | 101 | If you only want to receive news about new (non-alpha/beta) releases of |
| | 102 | Pidentd then you can join the 'ident-announce@lysator.liu.se' mailing |
| | 103 | list. Send mail to the address 'ident-announce-request@lysator.liu.se' to |
| | 104 | join it. No discussions will take place on this list. |
| | 105 | |
| | 106 | I also run a small mailing list for people who wants to act as testers |
| | 107 | of new alpha/beta-versions of Pidentd. If you wish to join, please send |
| | 108 | mail to the address 'pidentd-testers-request@lysator.liu.se'. (I can always |
| | 109 | use more testers, so don't hesitate :-) |
| | 110 | |
| | 111 | It's a human (namely me :-) that reads the letters sent to *-request. |
| | 112 | Please include the full email address to which to wish to have the |
| | 113 | letters sent. |
| | 114 | |
| | 115 | I'm grateful for success/failure stories about installing/compiling this |
| | 116 | daemon... |
| | 117 | |
| | 118 | Information of interrest: |
| | 119 | |
| | 120 | 1. Machine and operating system type and version. |
| | 121 | 2. Command line flags. |
| | 122 | 3. Inetd.conf configuration. |
| | 123 | 4. Did it work, or not. And if not - what did it report to the |
| | 124 | syslog file? (You'll have to add the "-l" option and probably |
| | 125 | reconfigure your Syslogd). If you use the "-d" option then |
| | 126 | you can see a verbose error if you Telnet into it directly and |
| | 127 | send it a query manually. (See the INSTALL file for more information). |
| | 128 | |
| | 129 | /Peter Eriksson <pen@lysator.liu.se>, 5 April 1993 |
projects / apple / network_cmds.git / blame_incremental