batch file horror.

  • Thread starter Thread starter Differentdays
  • Start date Start date
D

Differentdays

I've had a very dangerouse experience with MSAS:

I had explorer open in een directory on one of my drives (other than c:\
where windows is installed) and made a batch file by doing the following:
I right-clicked and choose for make a new text file. I named it rename.bat
(i've "show extensions" always on) and now I had an empty batch file.
I right-clicked it and choose for edit.
I typed in: ren *.* vac1*.* and closed the editor. (to rename all my photo's
from my first vacation)

When i executed the file, MSAS came up with a warning and a question if I
would block the file (action) or allow it.
I choose for allow (I know that what I did was right) and the batch file
executed.

NOW MY WHOLE c:\windows\system32 folder is full of files which are named:
vac1*.* !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
the original names of all sorts of file (DLL / EXE e.a.)
the batch excecution stopped when it came to the first file in-use
(luckely!!)

I've fixed the problems, but I think this is a BIG thing!!!

You could simply experience what I'm talking about by making a new
batch-file anywhere on your hd and make a line like this:

dir > list.txt

Execute the batch file, and you see the warning.
Choose for "ALLOW"

now NOT in the directory you excecute the batch-file, BUT in your SYSTEM32
folder you will find the file list.txt which contains the directory-listing
of your system32 folder....


p.s. I'm using the dutch version of windowsxp, so I would like to know if
annybody experience the same...
 
You are absolutely correct--both in your description of what happened and
that this is a serious issue.

This has been in the product from day one, and has been reported to the
development team. You can be assured that it will be fixed in the next beta
version distributed.

For a period of time, there was a Microsoft scripting guys article about
this issue which we could point people to, but that article disappeared some
weeks ago without explanation.

Frankly, there are a number of things that I sure wish had been done better
in this beta, and communicating known issues such as this one would be high
on my list.
 
Back
Top