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

feat(zed): pending-upstream-fix for GHSA-4grx-2x9w-596c, GHSA-c38w-74… #7284

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ritster
Copy link
Contributor

@ritster ritster commented Aug 21, 2024

…pg-36hr

- timestamp: 2024-08-21T21:48:03Z
type: pending-upstream-fix
data:
note: There is not currently a fixed version of the rsa crate. Currently, information about private keys is leaked via a side-channel timing attack, but work is underway to migrate to a fully constant-time implementation of the cryptography algorithm. So, we must wait for this implementation to be adopted by the rsa crate maintainers.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but work is underway to migrate to a fully constant-time implementation of the cryptography algorithm

could we include a link where someone could check in to see the current status of this if they wanted? Maybe to RustCrypto/RSA#19 ?

Comment on lines +131 to +134
- timestamp: 2024-08-21T21:48:03Z
type: pending-upstream-fix
data:
note: There is not currently a fixed version of the rsa crate. Currently, information about private keys is leaked via a side-channel timing attack, but work is underway to migrate to a fully constant-time implementation of the cryptography algorithm. So, we must wait for this implementation to be adopted by the rsa crate maintainers.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this whole advisory a duplicate of the CGA-g8r9-vv23-f4jf? Like because there's a duplicate GHSA? If so can we fix this in GHSA so we don't carry the duplicate in our data too?

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

Successfully merging this pull request may close these issues.

2 participants