We have finished the implementation of the next big cumulative patch for Veeam Backup & Replication 11 which brings vSphere 7.0 U2 support and have the release candidate build ready, however ran into a couple of unexpected issues with the code signing. One of them is actually quite interesting: our digital code signing provider suddenly dropped support for SHA-1 signatures, which we used in addition to SHA-256 signatures to ensure continued support for legacy OS which cannot process SHA-256 signatures. And it's hard to be mad at them since SHA-1 time has long passed, but now we need to make some unplanned build process changes. This also makes a good point for the recent topic of dropping support for legacy platform versions: even if we try our best to keep supporting them for as long as reasonably possible, the industry train as a whole cannot be stopped.
©GOSTEV