Skip to content
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

The Newtonsoft.Json.dll signing certificate is expired #2998

Open
Petr-Kovalev opened this issue Nov 6, 2024 · 4 comments
Open

The Newtonsoft.Json.dll signing certificate is expired #2998

Petr-Kovalev opened this issue Nov 6, 2024 · 4 comments

Comments

@Petr-Kovalev
Copy link

The Newtonsoft.Json.dll signing certificate is expired. Vaild to Tuesday, October 29, 2024 11:59:59 PM

Certificate
@JamesNK
Copy link
Owner

JamesNK commented Nov 7, 2024

Does this cause a problem?

@Petr-Kovalev
Copy link
Author

Hello James!

We got this stack trace in one of our products on a call to JsonConvert.SerializeObject(). I assume the certificate is the root cause.
I've added Newtonsoft.Json.dll assembly signing with our own certificate as a workaround. But decided to let you know. Someone else might have a similar issue.

Application: Workplace Container Helper.exe
CoreCLR Version: 8.0.1024.46610
.NET Version: 8.0.10
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException: Could not load file or assembly 'C:\Program Files (x86)\Workplace\Components\WorkplaceContainerComponent\Current\Newtonsoft.Json.dll'. Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (0x80070241)
File name: 'C:\Program Files (x86)\Workplace\Components\WorkplaceContainerComponent\Current\Newtonsoft.Json.dll'
   at Workplace.Logger.Formatters.FileLogFormatter.Format(IDetailedLogEvent logEvent)
   at Workplace.Logger.Writers.Rolling.RollingFileLogWriter.DequeueLogMessages()
   at Workplace.Logger.Writers.Rolling.RollingFileLogWriter.Flush()
   at Workplace.Logger.Logger.Flush()
   at Workplace.Logger.LoggerManager.Flush()
   at Workplace.Container.Api.Common.Logger.WorkplaceLogger.WorkplaceLoggerConfig.FlushLogs()
   at Workplace.Container.Helper.ContainerHelperRunner.<>c__DisplayClass4_0.<RunAsync>b__0()
   at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
   at Workplace.Container.Helper.Application.Main(String[] args)
   at Workplace.Container.Helper.Application.<Main>(String[] args)

@Petr-Kovalev
Copy link
Author

Important note, it was reproduced on Windows 11 24H2, not reproduced on Windows 10

@Petr-Kovalev
Copy link
Author

Petr-Kovalev commented Nov 24, 2024

Find out that the issue was actually caused by a call to SetProcessMitigationPolicy with enabled flag MicrosoftSignedOnly in PROCESS_MITIGATION_BINARY_SIGNATURE_POLICY.

So there is no issue with the current Newtonsoft.Json.dll signature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants