MaterialDesignInXamlToolkit
MaterialDesignInXamlToolkit copied to clipboard
MaterialDesignInXAML
Windows 11 - Smart App Control
Windows 11 is introducing Smart App Control. One of the security checks for apps is ensuring that the app and its binaries are signed. Because MaterialDesignInXamlToolkit does not sign its binaries, software using it will be blocked from running when Smart App Control is enabled.
Please sign DLLs produced for MaterialDesignInXamlToolkit.
https://support.microsoft.com/en-us/topic/what-is-smart-app-control-285ea03d-fa88-4d56-882e-6698afdb7003
Note: my project is using v3.2.0 of MaterialDesignThemes due to a dependency on .NET v4.5.
@hathawcs To my knowledge, the assemblies ARE signed. Perhaps they were not signed in version 3.2.0, that I do not know.
Both 3.20 and 4.8.0 do not have digital signatures. I believe they are strongly named though:
A signed component will have a Digital Signatures tab, such as this Microsoft dll:
When Smart App Control is in evaluation mode, you can see the failing apps in the Event Viewer. For example:
3076,"Code Integrity determined that a process (snipped) attempted to load \snipped\MaterialDesignThemes.Wpf.dll that did not meet the Enterprise signing level requirements or violated code integrity policy (Policy ID:{1283ac0f-fff1-49ae-ada1-8a933130cad6}). However, due to code integrity auditing policy, the image was allowed to load."
Both 3.20 and 4.8.0 do not have digital signatures. I believe they are strongly named though
Ah yes, my mistake. The key.snk is used for strong naming of course, not digital signatures.
even if the project start signing new releases i don't think they will go back and sign old versions and re-release them you might still have the same problem
even if the project start signing new releases i don't think they will go back and sign old versions and re-release them you might still have the same problem
That may be, but all of the software using MaterialDesignInXaml will fail to run when Smart App Control is enabled as it stands now. If the signing isn't backported to previous releases, users of MaterialDesignInXaml that can't update for "reasons" will be put in a bind.
even if the project start signing new releases i don't think they will go back and sign old versions and re-release them you might still have the same problem
That may be, but all of the software using MaterialDesignInXaml will fail to run when Smart App Control is enabled as it stands now. If the signing isn't backported to previous releases, users of MaterialDesignInXaml that can't update for "reasons" will be put in a bind.
you are assuming that everyone that's going to run a software that uses this library is going to run it on windows 11 and/or going to enable this feature also if it was that important to you and you are going to sign your app anyway your best option might be forking the library build and sign it yourself with the same certificate you used for the app
