Group your Dependabot Updates
Over the last week Dependabot has had more burr than usual, including a bunch of GitHub workflow updates for CodeQL, but bang, failed workflow.
Barry Dorrans rambles, pontificates, and muses on Microsoft .NET Security. Employed by Microsoft, but they don't want these opionins.
Over the last week Dependabot has had more burr than usual, including a bunch of GitHub workflow updates for CodeQL, but bang, failed workflow.
Recently, we’ve seen an increase in .NET vulnerability reports that fall into what we would call “bug-bug” territory rather than security vulnerability territory. To help guide future vulnerability research, we have a set of framing guidance.
A conversation with Azure Security about an unexpected behaviour when comparing Guid types in .NET demonstrated the need to explain how value versus representation comparisons can lead to security bugs.
A couple of weeks ago a friend asked what Server-Side Request Forgery (SSRF) was, how worried they should be, and how to fix it, as GitHub Copilot had told them that their application was vulnerable. This sent me down a rabbit hole thinking about my own .NET Bluesky SDK
How to use the Microsoft.SBOM.Targets NuGet package to produce a Software Bill of Materials (SBOM) during your release builds.
Windows Explorer can now show Git commit messages, the last changed date, and a version status of the file is modified and needs to be committed, as well as branch information in the status bar.
This guide will walk you through using a combination of GitHub actions and NuGet publishing policies to push packages to nuget.org from within an action without needing to worry about API keys.
This guide will walk you through using a combination of GitHub actions and Entra managed identities to enable signing code and NuGet packages from within an action without needing to worry about access tokens.
.NET 10 added ML-KEM, ML-DSA, SLH-DSA and Composite ML-KEM. Here I break down the support and its current limitations.
A breakdown the year in .NET CVEs, including the code that caused the vulnerability, the fixes, and links to the GitHub PRs or commits that fixed the issues.