-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Public Nodes Firewall rules #7924
Comments
https://github.com/monero-project/meta/blob/master/VULNERABILITY_RESPONSE_PROCESS.md (which, btw, is right there in the README of this repository) yes, might be worth pointing to that entry from |
then @moneromooo and @luigi1111 are needed here , there are only few hackativity reports on hackerone and the ones less than 1 year ago aren't accessible , why #7830 isn't submitted to hackerone i think that is as critical issue as this one https://hackerone.com/reports/501585 |
|
This wasn't a problem in the last years. If someone has a vulnerable machine there isn't much we can do. |
The Monero.fail lists and the public_nodes command of the cli wallet , generates an ultimate attack surface for adversaries with a bunch of vulnerable machines with a lot of open ports from different ISPs ,how was the monero community handling this in the past years ? , and where is the roadmap ? , its very hard for open source communities to maintain a long term roadmap or plan unless they are backed with whales , i think that was the case when RandomX was Launched , finally why is the security policy section of the github is neglected even in the most active projects out there ?
The text was updated successfully, but these errors were encountered: