From owner-freebsd-hackers Sat Jul 10 10:13:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 105F914C05; Sat, 10 Jul 1999 10:13:01 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id TAA13461; Sat, 10 Jul 1999 19:12:59 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199907101712.TAA13461@gratis.grondar.za> To: "Brian F. Feldman" Cc: hackers@FreeBSD.ORG Subject: Re: a BSD identd Date: Sat, 10 Jul 1999 19:12:58 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is it worth it to write an identd for FreeBSD? With one sysctl added, it's > trivial to implement. If an identd would be desired, then should I make a > separate one, or rewrite the current inetd's internal identd shim? I > don't see a reason for pidentd when we could have an identd built in by > me fixing inetd up, and it would all take up less space. There is the question - what for? identd is of questionable use at best. The best use of identd I have seen is crypted cookies that would allow an attackee to identify an attacker in a non-privacy-invasive manner. In 3 years of running this at an ISP, I have never seen it used in anger. Under normal circumstances (${BIGNUM} Wintendo boxes running IRC clients), the info given is completely useless. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message