Is Vulndetect shy? Do not recommend Agent 2.0.0
Agent 2.0.0 released but not recommended. Shy ?
I am quite sure I won't wait long.
In VulnDetect - Personal you can update by clicking the blue Update button.
In VulnDetect - Corporate you can update by clicking the blue "Approve Version in Selected Approvals" under Patching->Approvals. The green "Automate Selected Approvals" does not yet have any effect, as this would automatically update the majority of our customers. We would still like to test a bit more, before it goes out to a huge number of hosts.
Agent 220.127.116.11 is out, feel free to test it. There is only a small change from 18.104.22.168, which ensures that the agent doesn't cause all users from an AD to be queried.
We hope to "recommend" it soon and roll it out to a broader audience.
We've planned to make a new version with a fix for the AD issue this week.
Once it is out, we just need to confirm that the issue is resolved, and then I think we are good to distribute it more widely.
@olli_s Yes, we should announce it. But we are going slowly with this one, because it is a major upgrade.
And today we learned that we pulled a bit too much info from corporate ADs, despite a filter on the query.
So we are working on ways to solve this, we did not determine if we can fix this in the backend or if it requires a new agent.
Before this is solved, we won't announce or push 22.214.171.124 further.
However, it should be perfectly good for all private PCs.
Even I did not know that Version 126.96.36.199 of the VulnDetect agent is out.
I just got this information here in the forums.
@Tom You can/should me inform about new versions of the agent, so I can test it.
@tom : Upgrade done before my post on at least one system. I will suggest to my children to upgrade.
May I suggest to post something on Announcements.
Yes, we are very slow in recommending the new agent...
Well, the reason is that we need to roll it out on 100's of company networks, and we need to test it very thoroughly.
Although it has undergone internal testing for almost three months, we still want to wait a bit, before we mass upgrade on customer systems.
Please feel free to upgrade to 188.8.131.52, there shouldn't be any issues. We will also upgrade a few customers in the coming week, and if that goes well, then we will start to recommend 184.108.40.206 and thus enabling automatic upgrades.
220.127.116.11 enables our new packages, which in turn will allow upgrading per-user installs, not only system-wide like today.