How does Ranger verify that my plug-in is digitally signed?
Prior to loading your plug-in, Ranger will verify that your plug-in is
signed with Silver Bullet's digital signature. ilver Bullet will sign
the released version of your plug-in after it passes Ranger
certification testing.
There is one exception to this
case. If a Ranger developer license file is present, Ranger will load
your plug-in even if it is not signed. This allows you to make changes
to your plug-in prior to Ranger certification testing.
You're not allowed to give your Ranger developer license file to customers or other companies without written permission from Silver Bullet.
Related Articles
Silver Bullet Signed Certificate Policy
Silver Bullet Technology, Inc. has the ability to use Web Socket Secure (WSS) communications with its Ranger Remote client/server platform. This security layer requires the use of signed certificates to create this secure connection. For the security ...
What is the plug-in certification process?
Since our certification process is evolving, we will not charge you for the first certification. There are the high-level certification steps: Send us a scanner to test with. Email us your plug-in some source code and TransportInfo.ini and ...
Where are scanner plug-in files located?
The default program file location for a Ranger scanner plug-in is: C:\Program Files\Silver Bullet Technology\Ranger\Scanner Plug-ins\[plug-in name]\ Windows Vista: C:\ProgramData\Silver Bullet Technology\Ranger\Scanner Plug-ins\[plug-in name]\ ...
How will my plug-in be installed?
You'll create an installation script based on the sample installation script in the plug-in SDK. Your plug-in installer will install and uninstall all of the device drivers, DLL and support files needed to run your plug-in. During the plug-in ...
How can my plug-in define unique parameters?
Each plug-in has an ini file for setting options that are unique to the scanner(s) that the plug-in supports. You specify which options are available by placing an ini file with the same root name as you plug-in DLL in the plug-in data directory ...