-
Notifications
You must be signed in to change notification settings - Fork 526
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
Add Monero to Supply Chain Compromises #822
Comments
This issue has been automatically marked as inactive because it has not had recent activity. |
@maltfield thanks for opening the issue - would you be willing to make a PR for this? |
This issue has been automatically marked as inactive because it has not had recent activity. |
@lumjjb I would like to help to do this PR |
This issue has been automatically marked as inactive because it has not had recent activity. |
@lumjjb can the PR be reviewed so this can be closed? |
sorry that i missed this - i added a comment and updated the branch. Once we address the comments and CI passes ill merge it! |
This curated list of Supply Chain Compromises is awesome, thanks for maintaining it!
I noticed that the Monero wallet's compromised release from 2019-11-18 is not listed in this repo.
Considering that Monero is widely considered to be the most popular/secure privacy cryptocurrency, it's easily one of the most security-critical packages that you wouldn't want to become victim to supply chain attacks..
Fortunately, they did have release signing in-place, so users were quickly able to identify the issue and address it. But it's yet another cautionary tale for project maintainers that blindly trust their infrastructure.
Further reading on this incident:
The text was updated successfully, but these errors were encountered: