@olli_s Yes, I noticed yesterday, it should be gone. It was from an old page on their site
Posts made by Tom
RE: 1Password - Alter Product Name
I think their naming is a bit inconsistent:
Since they use "for Windows" on their changelog/update page, then we will stick with this for now.
RE: Create Log-Folder before Scanning
This is scheduled to be changed in one of the next two upcoming releases of the VulnDetect agent. Massive additions are planned for the agent in the coming weeks, but I can't promise that the log issue will be fixed in the first release.
You can always run it using
secteer.exe -l c:\users\<youruser>\somefilename.logif you need the log or create the folder like you suggest.
RE: SecTeer Personal VulnDetect (Alpha) launched today
Today we released a new version of the agent, this has been updated to exclude certain system folders:
The new agent can be downloaded from:
We recommend that you upgrade to the new version, as your inspection results will be more accurate.
In the future we will make a separate post for every release we make of the binary (agent) and the UI.
RE: [Implemented] Don't store log files in the Windows folder
VulnDetect is intended to be run in an automated manner, using the scheduling. When it runs in this manner, it has the required privileges to store log files (and read all applicable files).
If you run VulnDetect as a "normal" user, which works fine for most, you should be aware that there is a number of potential issues, since VulnDetect doesn't necessarily have the privileges to read all relevant files on the system.
This also goes for the logging, so if you want log details, while running VulnDetect as a "normal" user, you should either view directly on the console (so no -q) or you should specify "-l c:\users\myuser\mylogfile.log" and again, no "-q" since it also makes logging quiet.
So, all in all, if you want correct (complete) results, you should either only use the scheduled inspection or run "secteer.exe" as an administrative user. Running "secteer.exe" directly should only be used for a quick update of your results or for testing.
On another, but related, note, we will soon be launching a new feature in VulnDetect, which also will require higher privileges, so again, running "secteer.exe" directly is only for quick troubleshooting or testing of newly added rules / apps.
RE: Show "VulnDetect Scan" Desktop Icon
@olli_s I'm afraid that a "VulnDetect" prefix like that could cause issues with potential new products that we make. Thus, a construction like the one you have with "GetAppDetails for VulnDetect" is much more appropriate.