Difference between revisions of "Interface"
m (→Scan ResultS) |
(→Usage: added var types) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | Searches the registry interface list for interfaces with the given name, pointing to the given class. | + | {{SbiCmdInfo |
| + | |SYNTAX = Interface | ||
| + | |PENAME = SpybotSD.exe | ||
| + | |PEVERSION = 1.3 or later | ||
| + | |GROUP = Registry | ||
| + | |MINUPDATE = n/a | ||
| + | |ADVFILEPARAMS = no | ||
| + | |ADVREGPARAMS = no | ||
| + | |ADVBUILDPARAMS = yes (fourth) | ||
| + | |ADVSPECIALPARAMS = no | ||
| + | }}Searches the registry interface list for interfaces with the given name, pointing to the given class. | ||
==Usage== | ==Usage== | ||
| − | Interface:<interface | + | Interface:<interface(string)>,<linkedclass(string)>[,linked typelib name[,advanced build parameters]] |
===Examples=== | ===Examples=== | ||
Latest revision as of 16:21, 22 February 2008
| Interface | |
| Group | Registry |
| Main Application | Version 1.3 or later |
| Required Update | n/a |
| File Parameters | no |
| Registry Parameters | no |
| Build Parameters | yes (fourth) |
| Special Parameters | no |
Searches the registry interface list for interfaces with the given name, pointing to the given class.
Usage
Interface:<interface(string)>,<linkedclass(string)>[,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.
