Did you just download a file that has a digital signature from AppSense and wonder if the file is safe? If so, please read on.
You'll typically see AppSense when double-clicking to run the file. The publisher name is displayed as the "Verified publisher" in the UAC dialog as the screengrab shows:
You can view the digital signature details for AppSense with the following procedure:
Here's a screenshot of a file signed by AppSense:
As you can see in the screenshot above, Windows states that "This digital signature is OK". This implies that the file has been published by AppSense and that no one has tampered with the file.
If you click the View Certificate button shown in the screenshot above, you can examine all the details of the certificate, such as when it was issued, who issued the certificate, how long it is valid, etc. You can also view the address for AppSense, such as the street name, city and country.
VeriSign Class 3 Code Signing 2010 CA and VeriSign Class 3 Code Signing 2004 CA has issued the AppSense certificates. You can also see the details of the issuer by clicking the View Certificate button shown in the screenshot above.
The following are the AppSense files I have collected, thanks to the FreeFixer users.
Detection Ratio | File Name |
---|---|
0/45 | EmLoader.dll |
0/59 | amapph~1.dll |
0/58 | amapph~1.dll |
The detection percentage is based on the fact that I have gathered 162 scan results for the AppSense files. 0 of these scan reports came up with some sort of detection. If you like, you can view the full details of the scan reports by examining the files listed above.
The analysis is based on certificates with the following serial numbers: