BTCPay Server

This commit is a routine infrastructure change: BTCPay Server is switching its automated testing and release system from CircleCI to GitHub Actions. It copies the same test scripts, signing checks, and Docker publishing steps into GitHub Actions workflows. There is no change to the actual BTCPay Server application code that users interact with, and nothing in the commit suggests a security vulnerability was fixed or introduced.

This commit changes how BTCPay Server validates payment method settings so that the store object is passed into the validation process. The change itself only adds a new piece of information (the store) to validation contexts; it does not by itself fix a visible bug or block an attack. Without the rest of the related code, it is unclear whether this prevents a security issue or is just a refactoring/cleanup step.

This commit removes two contradictory sentences from an internal documentation file that tells contributors how to write pull request descriptions. One sentence had told them not to write about testing strategy, while another told them to add a testing note. The change only affects contributor guidance, not the BTCPay Server software that users or merchants interact with.

This is a tiny one-line change to a unit test helper that fetches cryptocurrency exchange rates from BTCTurk. It adds an extra sanity check: it ignores any exchange rate where the bid price (what buyers are offering) is higher than the ask price (what sellers are asking), because that is an impossible/inverted market state. The commit message says it is fixing a flaky test, not a security bug.

This commit rewrites how BTCPay Server performs host-level maintenance. Instead of the web application opening SSH connections directly to the host, it now runs a local helper program called 'btcpay-host'. The Docker image includes a wrapper that can still forward those calls over SSH, but the core application no longer needs SSH credentials or the SSH.NET library. The change removes a large amount of SSH-related code and adds a new plugin for maintenance actions. It is primarily an architectural/security-hardening change rather than a clear-cut fix for a single vulnerability.

This is a one-line change to a test file. It updates a test case that checks for a duplicate email error so that it also provides a current password. The change does not modify any production code and has no direct security impact on the BTCPay Server application itself.

This is a broad security patch for BTCPay Server 2.4.3. It fixes several access-control gaps (for example, lower-privileged store users could manage server admins or see sensitive API keys), hardens user-profile changes by requiring the current password, removes a third-party comment system (Disqus) that could inject scripts, adds rate limits to public invoice creation, stops plugins with known incompatibilities from loading, and tightens validation of Bitcoin transactions and multisig wallet setup. The changelog explicitly calls it a security release and recommends updating for multi-user servers.

This commit only edits the wording of a changelog entry for BTCPay Server 2.4.2. It does not change any code, configuration, or executable files. The edit makes the release sound more urgent, but the commit itself is purely documentation and contains no security fix.

This commit marks several public methods on ASP.NET Core controllers with [NonAction], which prevents them from being exposed as web-accessible HTTP routes. Without this attribute, these helper methods could be reached directly via URL, potentially allowing users to bypass intended workflows, access internal logic, or trigger actions that were only meant to be called by other controller code. The change is a hardening fix rather than a clear-cut exploit patch, because the diff alone does not show that any of these routes were actually reachable or dangerous in practice.

This commit is a version bump and changelog for BTCPay Server 2.4.2. The changelog describes two security-related changes: disabling Basic authentication by default shortly after account creation, and fixing a TOTP two-factor authentication bypass when using Greenfield Basic authentication. The actual code fixes are not shown in this commit, so we can only see the vendor's description of the issues. The vendor rates these as 'not critical' but still recommends updating.