On Tue, 13 Feb 1996, Kyle Amon wrote:
> Is there any reason (other than the loss of remote user identification
> services on my host) that I might _not_ want to disable identd?
I think it's one of those "You scratch my back, I'll scratch yours"
things. Identd is definitely an "administrator-friendly" protocol.
Disabling identd will not be directly detrimental to your site, unless you
have lots of IRC users and that is a service which your site policy
provides. Some IRC channels do not allow users from hosts that do not have
identd running properly (or at all).
>If every site were to disable identd, then many web servers and
>network-access monitoring tools would be "crippled" wrt logging.
That's an interesting statement. I agree that if a sys admin disables identd
machines, then he risks shutting off his users from a large amount of sites
(since many now run the RFC pidentd or in.identd. However, I don't believe
that identd is of any use at all from any other perspective because it is SO
easy to spoof. For example the freely distributed "jidentd" package for linux
that allows users to specify any username they want in a jidentd.liar file,
and that username is given out for identd requests.
What is the point in using a user identification service, when you can't even
rely on the information it yields?
_/_/_/ _/_/_/ _/_/_/ _/_/_/ | Tel: (0141) 337 5000
_/ _/ _/ _/ | Fax: (0141) 337 5050
_/_/_/ _/ _/_/ _/ | Net: scet @
_/ _/ _/ _/ | AppleLink: SCET.DEV
_/_/_/ _/_/_/ _/_/_/ _/ |
......learning through technology |