This is not a great experience for anyone. If we had customers running their own security solutions, we'd have to explain that it's flagging it because Veeam won't use SemVer and don't think it's important to put the patch number into the correct part of the registry so EVERYTHING knows what version of their product is installed and if it's vulnerable etc. That's not going to make Veeam look good.
Even if you won't switch to plain SemVer, PLEASE can you write the WHOLE version string to
Code: Select all
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID-HERE}]
"DisplayVersion"="a.b.c.d Pyyyymmdd"Code: Select all
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID-HERE}]
"DisplayVersion"="a.b.c.d.yyyymmdd"So other software can consume the exact version number, and amongst other things correctly determine if the software has a known security vulnerability in it?
Thanks
will see. What I was explaining above about the current approach being a major time saver for R&D is true. But then there's all the feedback and frustrations above which of course would be nice to address. So we gave it a fair go and made an attempt to switch the approach right after V12... but quickly decided not to pursue due too many challenges that would have potentially delayed V12 patches for a very long time. But we're now making preparations directly in 12a code base and will "try again later"!
