This is disabled by default, if you wish to get access and test this, please write to tom at vulndetect dot com or send us a message on the chat (@tom).

Please note that this is functionality from the Corporate edition and that the UI part of it will be completely redone. The underlying technology will remain the same for both Personal and Corporate.

You can find the updated changelog here:
https://vulndetect.org/topic/472/release-secteer-vulndetect-personal-and-backend-20-11-2019

• UI & backend
• Agent

We've been a bit silent lately, mostly because we've been extremely busy.

Today we updated the changelogs, so you can get an idea of the recent changes.

What is less clear when reading the changelogs is the upcoming addition to SecTeer VulnDetect:

• Automated updates

We will launch a "tech preview" of the automatic updating capability this week - this will be an "opt-in" feature for a while. Mostly, because we need volunteers to test the quality of the updates, especially the support for localized versions and 32/64bit architecture is important to test.

Please write to "tom [at] vulndetect [dot] com" if you wish to enable auto updating and help testing.

The automated updates in SecTeer VulnDetect is powered by chocolatey, usually referred to as choco. Initially SecTeer will provide homegrown packages from our own repo only. Later we may add support for third party repos, including the official choco repo. We chose to use choco, because this a popular, established and well maintained open source project, that aims to "packify" software management. Today, most software on Windows is managed by a variety of installers and update mechanism, the goal of standardizing this is beautiful and we would like to support those efforts.

In turn choco uses an official Microsoft package standard called NuGet.

/Tom

The new agent can be downloaded from:
https://vulndetect.com/dl/secteerSetup.exe

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.

This is because some browser (Firefox, maybe more) caches the permanent redirect (301) that we had on https://vulndetect.com/?1 when changing domains for the forum.

To fix this you either have to use another browser or clear your cache in Firefox.

And we learned that we need to do temporary redirects (302) if we plan to reuse a URL / domain for something else.

See:
https://vulndetect.org/topic/403/approving-account-on-vulndetect-com

We currently have a small backlog of rules in need of updating because we have been focused on the transition from CARMA to VulnDetect.

But we are now back to working on the rules.

Please do report any discrepancies in the rules, right now our focus is to get back on track with the software we already detect. And then in a week or two we will start adding new software again.