Difference between revisions of "Interface"
| Line 16: | Line 16: | ||
Using [[RegyKey]] along with [[Advanced registry parameters|advanced registry parameters]] might be an alternative to this command under many circumstances, make sure you really need this one before you use it! | Using [[RegyKey]] along with [[Advanced registry parameters|advanced registry parameters]] might be an alternative to this command under many circumstances, make sure you really need this one before you use it! | ||
| + | |||
| + | ==Scan ResultS== | ||
| + | * Only the registry key of the ''Interface'' itself gets flagged, which is important since not all linked entries may be as bad as the ''Interface'' itself. | ||
==See also== | ==See also== | ||
Revision as of 12:08, 18 February 2008
Searches the registry interface list for interfaces with the given name, pointing to the given class.
Usage
Interface:<interface name>,<linked class name>[,linked typelib name[,advanced build parameters]]
Examples
Interface:"clsSpyingContent","PSOAInterface"
Description
Similar to CLSID, this is outdated and should only be used in cases where the related GUIDs are very random.
- The first parameter specifies the name of the interface to be detected.
- The second parameter specifies the name of the class that the interface is linked to as an additional criterion. Algo-Prefixes are supported after 1.5.2 only. AP
- Optionally, you may also provide a name of a typelib associated to further limit the detetection, as a third parameter. Algo-Prefixes are supported after 1.5.2 only. AP
- Fourth comes the dvanced build parameters that allow you to limit the detection to specific Spybot-S&D versions.
Using RegyKey along with advanced registry parameters might be an alternative to this command under many circumstances, make sure you really need this one before you use it!
Scan ResultS
- Only the registry key of the Interface itself gets flagged, which is important since not all linked entries may be as bad as the Interface itself.
