Re: [saag] should we revise rfc 3365?

Mouse <mouse@Rodents-Montreal.ORG> Thu, 24 May 2012 03:39 UTC

Return-Path: <mouse@Sparkle.Rodents-Montreal.ORG>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C52F611E80B6 for <saag@ietfa.amsl.com>; Wed, 23 May 2012 20:39:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.945
X-Spam-Level:
X-Spam-Status: No, score=-8.945 tagged_above=-999 required=5 tests=[AWL=0.443, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pVwU5xsmBYLE for <saag@ietfa.amsl.com>; Wed, 23 May 2012 20:39:45 -0700 (PDT)
Received: from Sparkle.Rodents-Montreal.ORG (Sparkle.Rodents-Montreal.ORG [216.46.5.7]) by ietfa.amsl.com (Postfix) with ESMTP id CDBA811E8091 for <saag@ietf.org>; Wed, 23 May 2012 20:39:44 -0700 (PDT)
Received: (from mouse@localhost) by Sparkle.Rodents-Montreal.ORG (8.8.8/8.8.8) id XAA25498; Wed, 23 May 2012 23:39:43 -0400 (EDT)
Date: Wed, 23 May 2012 23:39:43 -0400
From: Mouse <mouse@Rodents-Montreal.ORG>
Message-Id: <201205240339.XAA25498@Sparkle.Rodents-Montreal.ORG>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Erik-Conspiracy: There is no Conspiracy - and if there were I wouldn't be part of it anyway.
X-Message-Flag: Microsoft: the company who gave us the botnet zombies.
X-Composition-Start-Date: Wed, 23 May 2012 23:31:54 -0400 (EDT)
To: saag@ietf.org
In-Reply-To: <4FBD873D.3090802@isi.edu>
References: <4FBD6A78.2070204@cs.tcd.ie> <201205232351.TAA23415@Sparkle.Rodents-Montreal.ORG> <4FBD873D.3090802@isi.edu>
Subject: Re: [saag] should we revise rfc 3365?
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2012 03:39:45 -0000

>> [RFC 3365]
> To open a can of worms, this would also be a good doc in which to
> discuss the need for secure ports, and whether (or not) to ever
> assign meaning to the difference between system and user ports...

I submit that attempting to make such a distinction is effectively
meaningless, and has been ever since single-user machines - machines
owned personally by individuals who are their administrators - became
even moderately common.  It meant something (though even then not much)
in the days of large multi-user machines whose administrators could
reasonably be treated by the rest of the net as more trusted than the
bulk of their users.  Those days are long past; between personal
machines and pwn3d windows boxen, I think it is now pointless.

To look at it another way, there can be no distinction between system
and user ports from the point of view of network-observable behaviour,
since the "system"-vs-"user" distinction, to the extent that it exists
at all, is entirely private to each host; it is, therefore, pointless
to try to mandate any such difference.

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		mouse@rodents-montreal.org
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B