Apparently an expired NuGet certificate has today caused .NET 5 projects to stop working on Debian Linux, according to multiple reports.
About 10 a.m. EDT a post on the Hacker News development-oriented social site declared: “All .NET 5 projects build failing because MS certificate has expired.”
That was quickly followed by this post: “.NET NuGet Package Validation Broken: Certificate Expired.”
The NuGet organization quickly published its own post (issue #10591) titled “NuGet restore failing on .NET 5 for Debian-based OSes (CA trust changed).”
Approximately four hours later NuGet followed up on the matter with issue #49 titled “NuGet restore failing on .NET 5 for Debian-based OSes.”
In the latter post, NuGet said, “Our preliminary investigation shows that .NET 5 restore is broken for Debian-based operating systems including Docker.” Furthermore, Debian 10 (“buster”) and earlier versions are affected, but not Debian testing (“bullseye”) and later.
“This is because of an issue reported in the
ca-certificates package in which the root CA being used are not trusted and must be installed manually due to Symantec Issues. Because this issue has been resolved recently in version 20210119 of this package, it is not available in a Debian version as provided in
The latter NuGet post (#49) lists three workarounds and a solution, which reads:
ca-certificates package is due to be installed in the Debian FTP archive which will promote this fix to the buster release in the next few days to which an updated
buster-slim image will be prepared and released when available.
NuGet said it would post updates on issue #10491 and #49.
About the Author
David Ramel is an editor and writer for Converge360.
Rust, one of the fastest-growing programming languages, is the subject of a new Visual Studio Code topic.
Dr. James McCaffrey of Microsoft Research explains the machine learning technique, which can be used to predict a person’s happiness score from their income and education, for example.
Visual Studio 2022 for Mac 17.0 Release Candidate 2 has shipped, cleaning up some issues reported by developers trying out the previous release candidate.
Explorer file nesting is now no longer experimental, along with default bracket pair colorization, new functionality for find all references in markdown and much more.
Microsoft recommends replacing relic from old .NET Framework with Blazor, but you can still do ASP.NET Web Forms apps in Visual Studio 2022 if you want to, with a couple tweaks.
> More Webcasts
Problems? Questions? Feedback? E-mail us.