[Solved] Is Vulndetect shy? Do not recommend Agent 2.0.0

OLLI_S

Even I did not know that Version 2.0.0.0 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

@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 2.0.0.0 further.
However, it should be perfectly good for all private PCs.

OLLI_S

@tom said in Is Vulndetect shy? Do not recommend Agent 2.0.0:

@olli_s Yes, we should announce it. But we are going slowly with this one, because it is a major upgrade.

All good, @Tom!

Tom

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.

Tom

Agent 2.1.0.0 is out, feel free to test it. There is only a small change from 2.0.0.0, 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.

Tom

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.

GregAlexandre

@OLLI_S : fixed

Tom

@gregalexandre Indeed, 2.1.0.0 is recommended and more than 95% of all hosts are upgraded already.

GregAlexandre

@tom : That why I suggested to OLLI_S to move this topic to the resolved issues directory.
No problem with the latest version, as with previous one!
Regards.
Greg

OLLI_S

OK, then I mark this issue as solved.