You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When someone connects to any public Ergo node, they get information about the node. In my opinion, this should not happen. It should be a silent connection. I.e., if the node knows what it's connecting to, data is exchanged. If not, it's just a blank/silent connection.
E.g., this is what I see when I connect to my public Ergo endpoint from a simple Telnet connection:
ϡ��䯁�4gorefergo-mainnet-5.0.14
In contrast, if you telnet to one of my public relays on Cardano, such as telnet relays.bladepool.com 3001 it's a completely silent connection. Thus, a random person scanning ports would not know that this is a Cardano endpoint whereas an attacker scanning my Ergo endpoint, would know that it's Ergo-related and that I'm on version 5.0.14.
Just a thought for increased privacy.
Cheers!
The text was updated successfully, but these errors were encountered:
Hello Ergo Team.
First and foremost, thank you for all you do.
When someone connects to any public Ergo node, they get information about the node. In my opinion, this should not happen. It should be a silent connection. I.e., if the node knows what it's connecting to, data is exchanged. If not, it's just a blank/silent connection.
E.g., this is what I see when I connect to my public Ergo endpoint from a simple Telnet connection:
ϡ��䯁�4gorefergo-mainnet-5.0.14
In contrast, if you telnet to one of my public relays on Cardano, such as
telnet relays.bladepool.com 3001
it's a completely silent connection. Thus, a random person scanning ports would not know that this is a Cardano endpoint whereas an attacker scanning my Ergo endpoint, would know that it's Ergo-related and that I'm on version 5.0.14.Just a thought for increased privacy.
Cheers!
The text was updated successfully, but these errors were encountered: