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

Public Nodes Firewall rules #7924

Closed
AAH20 opened this issue Sep 8, 2021 · 5 comments
Closed

Public Nodes Firewall rules #7924

AAH20 opened this issue Sep 8, 2021 · 5 comments

Comments

@AAH20
Copy link

AAH20 commented Sep 8, 2021

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 ?

@cirocosta
Copy link
Collaborator

cirocosta commented Sep 8, 2021

finally why is the security policy section of the github is neglected even in the most active projects out there ?

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 .github/SECURITY.md, although I'd say it makes more sense to do so from a .github repository so it applies to all of them (see Creating a repository for default files)

@AAH20
Copy link
Author

AAH20 commented Sep 8, 2021

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

@UkoeHB
Copy link
Contributor

UkoeHB commented Sep 13, 2021

why #7830 isn't submitted to hackerone

  1. The issue is publicly known already.
  2. It takes a lot of work and expertise to make a PoC exploit.
  3. A hackerone report isn't going to get it solved faster.

@erciccione
Copy link
Contributor

why #7830 isn't submitted to hackerone i think that is as critical issue

We asked to the core team how to proceed. After looking into it they were ok with opening a public issue. See @UkoeHB's comment for the reasons.

@selsta
Copy link
Collaborator

selsta commented Feb 18, 2022

how was the monero community handling this in the past years ?

This wasn't a problem in the last years. If someone has a vulnerable machine there isn't much we can do. monerod isn't a firewall. Closing this as the other questions were also answered.

@selsta selsta closed this as completed Feb 18, 2022
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

No branches or pull requests

5 participants