-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebView2Loader assembly has a bad signature #462
Comments
That filed cannot be signed and makes our builds fail. More info: git-ecosystem/git-credential-manager#462
That file cannot be signed and makes our builds fail. More info: git-ecosystem/git-credential-manager#462
Yeah, I think this would be required if we're to keep Windows Broker/WAM support. I tried again to move GCM to .NET 6 ( |
It looks like this is less a problem with the WebView2Loader binary, nor the GCM distributed copy, but the Git for Windows package! git-for-windows/git#3332 (comment) Looks like Git for Windows' build was stripping off the PE signature and causing an invalid signature. This has been fixed in git-for-windows/build-extra#368 |
We've had several complaints that the WebView2Loader.dll binary that ships inside of GCM causes signing problems. First for getting Git for Windows submitted to the Microsoft Store (git-for-windows/git#1146 (comment)), and more recently problems with GitHub Desktop.
The WebView2Loader.dll comes in from our dependency on MSAL.NET's
Microsoft.Identity.Client.Desktop
package. We need that package on Windows to bring in support for WAM when targeting .NET Framework (as apposed tonetX-windows*
).The annoying thing is that we don't even use WebView2 because of various problems with it. We tried to move to .NET 5 on Window in the past and this resulted in an unacceptable bloat in binary size. When we turned all the optimisations/linking up to the highest level we only managed to reduce binary size a small amount, but broke things like UI.
We may have to drop WAM entirely. cc: @bgavrilMS
The text was updated successfully, but these errors were encountered: