Re: Valid characters on one o/s are invalid on another

["Craig Boston" <craig () aevrf gank org>]

Tested this both locally and over a network and the wildcard idea was able to
get rid of the files ending with a dot.  For the sake of being cautions,
"filename?" seems to be able to handle it as well without resorting to *

Win2k doesn't come with BASIC, so I snagged a copy of qbasic off one of the
NT4 machines.  It doesn't seem to understand long file names so I wasn't able
to do anything useful with it.

It seems these files (and possibly other files that the shell refuses to deal
with) can also be deleted by doing a DIR /X and deleting the DOS 8.3 name
directly.  Surprisingly, this seems to work on remote systems over the network
as well.

The shell should probably still be fixed as there are lots of clueless newbie
NT admins who don't know how to use the command-line...  Of course they
probably have bigger security problems anyway.

Craig

----- Original Message -----
From: "Meritt James" <meritt_james () bah com>
To: "James Robbins" <robbins.7 () osu edu>
Cc: "Craig Boston" <craig () aevrf gank org>; "Vuln-Dev"
<VULN-DEV () securityfocus com>
Sent: Wednesday, June 27, 2001 8:17 AM
Subject: Re: Valid characters on one o/s are invalid on another


I''ve zapped files with names containing illegal characters by using
wildcard that expanded to the particular file...

V/R

James Robbins wrote:
> I ran into a situation (quite a while back) where I had a file on a
> DOS machine that had illegal characters in it.  I couldn't rename
> or delete it.  I finally got rid of it by going into Basic and deleting
> it from there.  Since Basic requires the file name to be in quotes
> it accepted it and deleted the file.
>
> --
> James A. Robbins
> Network Engineer
> The Ohio State University
> Chemistry Department

--
James W. Meritt, CISSP, CISA
Booz, Allen & Hamilton
phone: (410) 684-6566