Difference between revisions of "Directory"
(→Usage: added var types) |
m (fixed location of advanced parameters (was: second)) |
||
Line 5: | Line 5: | ||
|GROUP = Files | |GROUP = Files | ||
|MINUPDATE = n/a | |MINUPDATE = n/a | ||
− | |ADVFILEPARAMS = yes ( | + | |ADVFILEPARAMS = yes (third) |
|ADVREGPARAMS = no | |ADVREGPARAMS = no | ||
− | |ADVBUILDPARAMS = yes ( | + | |ADVBUILDPARAMS = yes (third) |
|ADVSPECIALPARAMS = [[filename]] | |ADVSPECIALPARAMS = [[filename]] | ||
}}''Directory'' is the generic directly flagging command. | }}''Directory'' is the generic directly flagging command. |
Latest revision as of 21:53, 28 June 2008
Directory | |
Group | Files |
Main Application | Version 0.95 or later |
Required Update | n/a |
File Parameters | yes (third) |
Registry Parameters | no |
Build Parameters | yes (third) |
Special Parameters | filename |
Directory is the generic directly flagging command.
Usage
Directory:<description(string)>,<directory(string)>[,advanced directory parameters]
Examples
Directory:"<$DIR_PROG>","<$PROGRAMFILES>\Spyware\","filename=malware.exe,size>=100"
This example would detect the folder C:\Program files\Spyware\, if this folder contains a file malware.exe of at least 100 byte size.
Description
- The first parameter is a description; either as plaintext or, better, using a description template to have it appear localized in the scanner GUI.
- The second parameter defines the path to look in, using path templates and Algo-Prefixes if you want, where the later only affect the final folder, not the full folder path. AP PT
- Finally, the advanced directory parameters are very similar to advanced file parameters - in fact, the first one has to be filename to specify which file inside the folder should be checked for, but all further parameters are standard advanced file parameters. PT