Subject: Re: NetBSD Security Advisory 1999-008
To: Gerryt <gerryt@portal.ca>
From: Matthew Orgass <darkstar@pgh.net>
List: current-users
Date: 04/14/1999 18:51:04
On Wed, 14 Apr 1999, Gerryt wrote:

> On Wed, 14 Apr 1999, Matthew Orgass wrote:
> 
> :=>Date: Wed, 14 Apr 1999 17:54:00 -0400 (EDT)
> :=>From: Matthew Orgass <darkstar@pgh.net>
> :=>To: Simon Burge <simonb@telstra.com.au>
> :=>Cc: matthew green <mrg@eterna.com.au>,
>     current-users@netbsd.org
> :=>Subject: Re: NetBSD Security Advisory 1999-008 
> :=>
> :=>On Wed, 14 Apr 1999, Simon Burge wrote:
> :=>
> :=>> [[ CC list trimmed back to current-users ]]
> :=>> 
> :=>> > 	% ln -s ./ test
> :=>> > 	% ln -s ./ test
> :=>> 
> :=>> I don't get this problem with my 1.3.{almost4} pmax, either on a local
> :=>> ffs filesystem or an nfs filesystem.  Is this a "guaranteed to happen
> :=>> every time" problem?
> :=>
> :=>  I don't know the technical details, but apparently some ports don't have
> :=>it. It should happen every time on those that do.
> :=>
> :=>  However, the advisory was unclear in that on 1.3.3 it is not the ln that
> :=>triggers the hang but an ls afterwards.
> 
> It happens on i386 if you do the above exactly: enter it twice in a row.
> Then press reset...

  Err... oops.  My mistake, you only need the ls if you are linking a
different directory.

Matthew Orgass
darkstar@pgh.net