From owner-freebsd-security  Sun Nov  1 23:36:27 1998
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA25116
          for freebsd-security-outgoing; Sun, 1 Nov 1998 23:36:27 -0800 (PST)
          (envelope-from owner-freebsd-security@FreeBSD.ORG)
Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [205.162.1.28])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25111
          for <freebsd-security@FreeBSD.ORG>; Sun, 1 Nov 1998 23:36:26 -0800 (PST)
          (envelope-from jas@flyingfox.com)
Received: (from jas@localhost)
	by biggusdiskus.flyingfox.com (8.8.8/8.8.5) id AAA15786;
	Mon, 2 Nov 1998 00:32:12 -0800 (PST)
Date: Mon, 2 Nov 1998 00:32:12 -0800 (PST)
From: Jim Shankland <jas@flyingfox.com>
Message-Id: <199811020832.AAA15786@biggusdiskus.flyingfox.com>
To: dima@best.net
Subject: Re: SSH vsprintf patch. (You've been warned Mr. Glass)
Cc: freebsd-security@FreeBSD.ORG
In-Reply-To: <199811020647.WAA25893@burka.rdy.com>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

dima@best.net (Dima Ruban) writes:

> Let me ask you this. Would you trust a packet that came from
> non-priviledged port and which wants to do something that even
> remotely should be secure?

No.  Same as for a packet that came from a privileged port.

A packet's source port is a pretty weak authenticator, to coin
an understatement.

Jim Shankland
NLynx Systems, Inc.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message