Difference between revisions of "CLSID"

From SpybotWiki
Jump to: navigation, search
m (Description)
(Examples: added live help example)
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
Searches the registry for a class with the given name.
+
{{SbiCmdInfo
 +
|SYNTAX = CLSID
 +
|PENAME = SpybotSD.exe
 +
|PEVERSION = 1.3 or later
 +
|GROUP = Registry
 +
|MINUPDATE = n/a
 +
|ADVFILEPARAMS = no
 +
|ADVREGPARAMS = no
 +
|ADVBUILDPARAMS = no
 +
|ADVSPECIALPARAMS = no
 +
}}Searches the registry for a class with the given name.
  
 
==Usage==
 
==Usage==
  CLSID:[class name],<filename,<advanced file parameters>>
+
  CLSID:<class(string)>[,filename(string)]
  
 
===Examples===
 
===Examples===
 +
CLSID:"Spyware Class","<$SYSDIR>\spyware.dll"
 
  CLSID:"Dummy Class"
 
  CLSID:"Dummy Class"
  
This easy example would detect the following class:
+
The second example would detect the following class:
 
  [HKEY_CLASSES_ROOT\CLSID\{11223344-5566-7788-9900-AABBCCDDEEFF}]
 
  [HKEY_CLASSES_ROOT\CLSID\{11223344-5566-7788-9900-AABBCCDDEEFF}]
 
  @="Dummy Class"
 
  @="Dummy Class"
Line 13: Line 24:
 
===Description===
 
===Description===
 
Please do use [[RegyKey]] wherever the CLSID GUID itself is static; this command is reserved to identifying class IDs that are random and cn be identified only by their class name, or where you need to specify attributes of the associated file.
 
Please do use [[RegyKey]] wherever the CLSID GUID itself is static; this command is reserved to identifying class IDs that are random and cn be identified only by their class name, or where you need to specify attributes of the associated file.
 +
 
# The first mandatory parameter simply specified the exact name of the class.
 
# The first mandatory parameter simply specified the exact name of the class.
# The second, optional paraeter allows you to specify a file the class needs to point to to be flagged.
+
# The second parameter can be a substring of the ''InprocServer32'' filename. After 1.5.2, this also supports [[AlgoPrefix|Algo-Prefixes]]. {{AlgoPrefix}}
# The third parameter may only be specified if the second one is as well; it allows you to further limit the results down to classes for files that match certain [[Advanced file parameters|advanced file parameters]].
+
 
 +
===Scan Results===
 +
* The CLSID entry identified by the specified name.
  
 
==See also==
 
==See also==
* [[Advanced file parameters]]
+
* [[AlgoPrefix]]
* Sadly, no [[AlgoPrefix|Algo-Prefix]] here.
 
  
 
===Similar commands===
 
===Similar commands===
 
* [[Interface]]
 
* [[Interface]]
 
* [[RegyKey]]
 
* [[RegyKey]]
 +
* [[RootClass]]
 
* [[Typelib]]
 
* [[Typelib]]
  
 
[[Category:SBI Commands]]
 
[[Category:SBI Commands]]
[[Category:SBI Commands (outdated)]]
+
[[Category:SBI Commands supporting AlgoPrefix]]
[[Category:SBI Commands (current)]]
 

Latest revision as of 15:56, 22 February 2008

CLSID
Group Registry
Main Application Version 1.3 or later
Required Update n/a
File Parameters no
Registry Parameters no
Build Parameters no
Special Parameters no

Searches the registry for a class with the given name.

Usage

CLSID:<class(string)>[,filename(string)]

Examples

CLSID:"Spyware Class","<$SYSDIR>\spyware.dll"
CLSID:"Dummy Class"

The second example would detect the following class:

[HKEY_CLASSES_ROOT\CLSID\{11223344-5566-7788-9900-AABBCCDDEEFF}]
@="Dummy Class"

Description

Please do use RegyKey wherever the CLSID GUID itself is static; this command is reserved to identifying class IDs that are random and cn be identified only by their class name, or where you need to specify attributes of the associated file.

  1. The first mandatory parameter simply specified the exact name of the class.
  2. The second parameter can be a substring of the InprocServer32 filename. After 1.5.2, this also supports Algo-Prefixes. AP

Scan Results

  • The CLSID entry identified by the specified name.

See also

Similar commands