Re: Long path exploit on NTFS

From: Christophe Bousquet (c.bousquet@adilinstruments.com)
Date: 02/06/02 

From: "Christophe Bousquet" <c.bousquet@adilinstruments.com>
To: <bugtraq@securityfocus.com>
Date: Wed, 6 Feb 2002 07:52:47 +0100

Actually, you don't have to deal with long path name.

Here's a little experiment I've just done :
- a file with something that triggers my MacAfee VirusScan NT, put it in
    folder "Hello". Start scan : no problem, VirusScan warns me about
    the dangerous thing.
- same file, in folder called "nihongo", but labeled using japanese
    characters i.e. a folder with a unicode name. Start scan : nothing!
    No warning, because (i guess) no scan at all.

As Mr LeBlanc said, the problem here is those so-called NT version that
don't know what NT is.

Experiment done with VirusScan Engine 4.1.60, datfile 4.0.4183 on my
english NT 4.0 SP6+SRP+.. The bait I use is cdc's back orifice in a zip.

And for the little history, I don't blame MacAfee more than almost any
other app. I really hate it when xxxAmp can't play my jpop mp3, when
xxxCDCreator can't backup my folders on CD-R, etc...

Best regards
Christophe

** speaking for myself and *not* for my employer. **

Relevant Pages

  • personal2.xls appears and now all my triggers point to it
    ... folder. ... It is an exact duplicate - from what I can tell (it is not exactly ... I can go through, one by one, and reassign the triggers to my orig ... Is this a familiar situation to anyone? ...
    (microsoft.public.excel.programming)
  • Re: SSMS not displaying DB triggers
    ... The folder you mention only list DDL triggers. ... For DML triggers, expand the table in SSMS and you will see a trigger folder. ... Tibor Karaszi, SQL Server MVP ...
    (microsoft.public.sqlserver.tools)
Loading