[10734] in bugtraq

home help back first fref pref prev next nref lref last post

Re: Windows NT 4.0, 95, 98 (?) networked PRN flaw

daemon@ATHENA.MIT.EDU (Nick FitzGerald)
Mon Jun 7 13:08:06 1999

Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Message-Id: <199906070453.AAA02704@dub-img-ims-5.compuserve.com>
Date: 	Mon, 7 Jun 1999 16:49:24 +1200
Reply-To: nick@virus-l.demon.co.uk
From: Nick FitzGerald <nick@VIRUS-L.DEMON.CO.UK>
To: BUGTRAQ@NETSPACE.ORG
In-Reply-To:  <3.0.3.32.19990606114543.0376aca0@mail.mindspring.com>

> [lots and lots trimmed]
>
> I first encountered this a long time ago when I inadvertantly
> created a file named 'CON'.  Went round and round through most of
> the snippage trying to remove it.  What it boils down to is that
> anything that has the same name as a DOS device (which is a link to
> an actual device, just like you're used to seeing in /dev) is going
> to resist getting deleted and moved.
>
> The solution is to use a POSIX utility to remove it.  The POSIX

Whilst I'll assume that this is true (too much trouble to test it and
it sounds kosher), it is overkill for files.

Simple DEL CO? will nuke CON (and any other matching file).
MS-created GUI interfaces (File Manager, Explorer) tend to get in
the way.

In the case of directories it might not be so easy...


Regards,

Nick FitzGerald

home help back first fref pref prev next nref lref last post