From owner-freebsd-security Mon Jul 1 13:25:58 2002 Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4C5237B400 for ; Mon, 1 Jul 2002 13:25:55 -0700 (PDT) Received: from vec.nogood.org (CPE00045a0a55e6.cpe.net.cable.rogers.com [24.101.6.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC4E443E0A for ; Mon, 1 Jul 2002 13:25:53 -0700 (PDT) (envelope-from getsubmail@nogood.org) Received: from cport (cport.local [192.168.1.120]) by vec.nogood.org (8.12.5/8.12.5) with SMTP id g61KMc9V080708; Mon, 1 Jul 2002 16:22:38 -0400 (EDT) (envelope-from getsubmail@nogood.org) From: "getsubmail" To: "Eric Anderson" Cc: Subject: RE: SSH Patches Date: Mon, 1 Jul 2002 16:23:10 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <3D20A014.5B44DA36@centtech.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Importance: Normal Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Lupe Christoph wrote: > > > > > > No default install without a remote root in over 20 years. > > > > > I think you're wrong here. They didn't have a networking stack before > > > Windows 3.11 for Workgroups, in the early 1990s, so it's more like ten > > > years. > > > > So it's no remote in a default install for the first ten years? > > Wo! Read it again: > No default install without a remote root in over 20 years. > should be: > No default install without a remote root in over 10 years. > > The other way would be very wrong (remember, we are talking about > the big evil > here). That is it's no remote (capability) in a default install for the first ten years? C.N. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message