In addition to standard tools like antivirus, here are three additional heuristics you can use to determine if LogViewPlus can be trusted.
1. We are accountable. Clearcove Limited is registered in England and has been doing business online since 2006. Our company number is 6030104 which you can verify with the UK government. Clearcove is governed by English and European law - including GDPR.
LogViewPlus also licenses code from professional third party companies including Microsoft, DevExpress, RedGate and Rebex.
Accountability is a very important security guarantee that is not generally provided by open source software. LogViewPlus does not use open source software with the exception of the tar libraries from SharpZipLib. This code was manually reviewed before a one-time import.
2. All of our code is signed. You can verify this by opening the file properties on any of our executables. The file properties should include a "Digital Signatures" tab.
All of our executable code is signed with the name "Clearcove Limited". This signature is a cryptographically secure way of guaranteeing the code you are running is Clearcove Limited's responsibility. One advantage of a closed source application is that the chain of responsibility is crystal clear.
LogViewPlus should only be downloaded from LogViewPlus.com. If you do not see the "Clearcove Limited" signature on your executable, please let us know and DO NOT execute the software. Cracked software will be missing this signature.
3. Verify that LogViewPlus runs offline. LogViewPlus is a tool used by security professionals and is designed to run without a network connection.
You can verify LogViewPlus is running offline by checking the ports with netstat. This is done by executing two commands:
tasklist | findstr LogViewPlus.exe - Finds the process ID (PID) for the application. This command is case sensitive.
netstat -aon | findstr [PID] - Finds all ports currently used by the application.
Executing these two commands from the command line will show that, by default, LogViewPlus has only one port open:
The port is listening on the loopback address - so it is only accessible to processes running on the local machine. The port number is random and will likely change with each application restart.
This loopback port is used to run LogViewPlus in "single instance" mode. You can disable this listening port by allowing multiple application instances. This is done by deselecting the "Run only one application instance" checkbox in Application Settings:
After making this change, you can save your settings and restart LogViewPlus. There will now be no ports in use:
The only other time that you will see ports listed for LogViewPlus is if you have taken a user action which is obviously network related. For example, monitoring a remote data source, registering, or checking for application updates. LogViewPlus may also check for application updates shortly after start up. This check can also be disabled in Application Settings.
LogViewPlus currently has no outstanding issues with any antivirus provider. However, LogViewPlus is frequently updated. New updates may lead to suspicion from your anti-virus software until the update is fully trusted and the trust has been propagated. In some cases, propagation may take several days and during this time your anti-virus may take longer to analyze LogViewPlus. This is expected behavior as the anti-virus has no prior knowledge of the executable. False positives may also occur during this time, but in our experience these are rare.
If your antivirus provider is blocking LogViewPlus, please let us know.