-
Notifications
You must be signed in to change notification settings - Fork 63
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
Windows 11 - Smart App Control #55
Comments
I've verified the latest NReco.Logging.File nuget version and it is definitely strongly named (you can verify that with help of 'sn.exe' tool):
This means that it is compiled with If you need digitally signed DLLs for your app I believe that this should be done on your app's build (with help of sn.exe) - and all app's DLLs should be digitally signed with your key. |
Strong naming and digital signatures create more problems than they are worth. Because nefarious hackers can easily sign their own versions of various assemblies, with valid keys, they can easily negate goofy security schemes that require signing. That leads to attempts to maintain long allow lists for signers, which is arguably useful for system level files, but impossible to maintain on a global scale. It costs a lot of money to establish and maintain a publisher traceable signing chain. |
@hathawcs I can recommend signing the file yourself if you already have a signing chain |
Windows 11 introduced Smart App Control. One of the security checks for apps is ensuring that the app and its binaries are signed. Because NReco.Logging.File does not sign its binaries, software using it will be blocked from running when Smart App Control is enabled.
Please sign DLLs produced for NReco.Logging.File.
https://support.microsoft.com/en-us/topic/what-is-smart-app-control-285ea03d-fa88-4d56-882e-6698afdb7003
NReco.Logging.File (unsigned):
Microsoft dll (signed):
The text was updated successfully, but these errors were encountered: