Difference between revisions of "Interface"
| Line 1: | Line 1: | ||
| − | |||
Searches the registry interface list for interfaces with the given name, pointing to the given class. | Searches the registry interface list for interfaces with the given name, pointing to the given class. | ||
| Line 22: | Line 21: | ||
* [[CLSID]] | * [[CLSID]] | ||
* [[RegyKey]] | * [[RegyKey]] | ||
| + | * [[RootClass]] | ||
* [[Typelib]] | * [[Typelib]] | ||
[[Category:SBI Commands]] | [[Category:SBI Commands]] | ||
Revision as of 14:26, 17 February 2008
Searches the registry interface list for interfaces with the given name, pointing to the given class.
Usage
Interface:[name of interface],[name of linked class],<name of linked typelib>,<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.
- Optionally, you may also provide a name of a typelib associated to further limit the detetection, as a third parameter.
- 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!
