[10738] in bugtraq
Re: Windows NT 4.0, 95, 98 (?) networked PRN flaw
daemon@ATHENA.MIT.EDU (Terry Milnes)
Mon Jun 7 13:57:32 1999
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <375BB802.809F3750@interface.on.ca>
Date: Mon, 7 Jun 1999 08:16:02 -0400
Reply-To: Terry Milnes <tez@INTERFACE.ON.CA>
From: Terry Milnes <tez@INTERFACE.ON.CA>
X-To: "STEVENS, Eric" <Eric.Stevens@RP-RORER.COM>
To: BUGTRAQ@NETSPACE.ORG
Well I better clarify here, I did test this but misunderstood
the initial post, I started with Rm -d prn on the directory,
and of course it did delete, tried Rm prn on a file, it
deleted too, I quickly scanned the message, thought it said
something else so played with a couple of other ways and
posted....
So all of you out there who are wondering what is different
about my NT, nothing is different just the operator.
Terry...
"STEVENS, Eric" wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I suppose that, in an effort to maintain reverse compatibility with
> old MS-DOS command line gurus, you cannot create a file or directory
> named PRN.xxx where the xxx is replacable with any extension.
> Explanation and flaw follow.
>
> First, the explanation (for those of you who are familiar with the
