From owner-freebsd-stable Sat Nov 27 18:14:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from abc.123.org (123.org [195.244.241.123]) by hub.freebsd.org (Postfix) with ESMTP id 48D5514E27 for ; Sat, 27 Nov 1999 18:14:11 -0800 (PST) (envelope-from k@abc.123.org) Received: (from k@localhost) by abc.123.org (8.9.3/8.9.3) id DAA34580 for stable@freebsd.org; Sun, 28 Nov 1999 03:14:04 +0100 (CET) (envelope-from k) Date: Sun, 28 Nov 1999 03:14:04 +0100 From: Kai Voigt To: stable@freebsd.org Subject: finger(1) not RFC compliant Message-ID: <19991128031403.N19490@abc.123.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Organization: 123.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm not sure if I'm right and actually, there are more important things in the world. But while implementing the finger protocol in Pike, I found out that FreeBSD's finger(1) on my 3.3-STABLE does not behave as RFC 1288 wants it to. When entering "finger user@remotehost", finger has to send "/W user\r\n" to the remotehost. Instead, it sends "user\r\n" without the leading "/W ". In chapter 2.3, RFC 1288 defines a non recursive finger query as {Q1} ::= [ {W} | {W} {S} {U} ] {C} where {W} is "/W", {S} one or more spaces, {U} the username and {C} is "\r\n". Kai -- kai voigt hamburger chaussee 36 24113 kiel 04 31 - 22 19 98 69 http://k.123.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message