[16851] in bugtraq
Re: Double clicking on MS Office documents from Windows Explorer
daemon@ATHENA.MIT.EDU (Chip Andrews)
Wed Sep 20 14:48:25 2000
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <002b01c02308$65a33840$c206060a@claruscorp.com>
Date: Wed, 20 Sep 2000 09:40:53 -0400
Reply-To: Chip Andrews <chip@SQLSECURITY.COM>
From: Chip Andrews <chip@SQLSECURITY.COM>
To: BUGTRAQ@SECURITYFOCUS.COM
Has anyone explored the possibility of making use of Windows 2000 Private
DLLs to solve this issue? For example, the "side-by-side" approach could be
used to specify where DLLs for an application are stored to stop the search
path.
Older applications can be retro-fitted for private DLLs but using the
myapp.exe.local file to tell W2K to load DLLs from the directory where the
executable exists and not the search path or current directory.
Chip
----- Original Message -----
From: "Timothy J. Miller" <cerebus@SACKHEADS.ORG>
To: <BUGTRAQ@SECURITYFOCUS.COM>
Sent: Monday, September 18, 2000 4:56 PM
Subject: Re: Double clicking on MS Office documents
> I suggest that this problem, and subsequent problems of this nature,
> can be fixed simply by *not* looking in the current directory for
> required DLLs.
>
> -- Cerebus
>
