Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[release/9.0-staging] fix: in rsa signatures, configure digest before padding mode#115695

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged

Conversation

@github-actions
Copy link
Contributor

@github-actionsgithub-actionsbot commentedMay 18, 2025
edited by vcsjones
Loading

Backport of#114261 to release/9.0-staging

/cc@vcsjones@rcatolino

Customer Impact

  • Customer reported
  • Found internally

This was originally reported by a customer in#114260, and a request to back ported it was made in#115693.

Customers usingRSA.SignHash with RSASSA-PSS on Linux which is locked-down to FIPS are unable to use it because the configuration was done in such a way that confused the FIPS-only validation logic in OpenSSL. Customers have no work-arounds for this, other than do disable the FIPS enforcement on Linux.

Regression

  • Yes
  • No

No. It's been like this since we moved off the managed implementation of PSS padding for Linux.

Testing

This was manually validated on an Ubuntu Pro installation that was FIPS enforced.

Risk

Low. The code that configures the signing context has only changed in the order in which it does the configuration. The area has strong unit test covered to ensure existing scenarios did not regress.

IMPORTANT: If this backport is for a servicing release, please verify that:

  • The PR target branch isrelease/X.0-staging, notrelease/X.0.

Package authoring no longer needed in .NET 9

IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.

@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-system-security,@bartonjs,@vcsjones
See info inarea-owners.md if you want to be subscribed.

@bartonjsbartonjs added the Servicing-considerIssue for next servicing release review labelMay 20, 2025
@leecowleecow added Servicing-approvedApproved for servicing release and removed Servicing-considerIssue for next servicing release review labelsMay 22, 2025
@leecowleecow modified the milestones:9.0.x,9.0.7May 22, 2025
@jozkeejozkee merged commit397ee5f intorelease/9.0-stagingJun 9, 2025
98 checks passed
@jozkeejozkee deleted the backport/pr-114261-to-release/9.0-staging branchJune 9, 2025 15:59
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsJul 10, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.

Reviewers

@bartonjsbartonjsbartonjs approved these changes

Assignees

@vcsjonesvcsjones

Labels

area-System.SecurityServicing-approvedApproved for servicing release

Projects

None yet

Milestone

9.0.7

Development

Successfully merging this pull request may close these issues.

6 participants

@bartonjs@vcsjones@leecow@jozkee@rcatolino

[8]ページ先頭

©2009-2025 Movatter.jp