If Microsoft is not planning on providing a fix for this until Vista, I can see a worm coming from this. Forgive me if I don't know how this works in the windows world, but when it is looking for this DLL, does it take the first one that it finds within your path; like in UNIX? Or does it look in all directories within your path and then decide? I am guessing the former, but I am just clarifying.
<br><br><div><span class="gmail_quote">On 11/3/06, <b class="gmail_sendername">Eliah Kagan</b> <<a href="mailto:degeneracypressure@gmail.com">degeneracypressure@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 11/2/06, Roger A. Grimes wrote:<br>> So, if you're statement is accurate that malware would need to be placed<br>> in a directory identified by the PATH statement, we can relax because<br>> that would require Administrator access to pull off. Admin access would
<br>> be needed to modify the PATH statement appropriately to include the<br>> user's desktop or some other new user writable location or Admin access<br>> would be needed to copy a file into the locations indicated by the
<br>> default PATH statement.<br><br>It would not require *administrator* access--non-administrator users<br>can still add things to their own PATHs, just not to the universal,<br>system PATH. (See Control Panel > System > Advanced > Environment
<br>Variables.)<br><br>-Eliah<br></blockquote></div><br><br clear="all"><br>-- <br>Thx<br>Joshua Gimer