restricting access to nodes bitcoind talks to

MoonShadow

legendary

Activity: 1708

Merit: 1010

Quote from: xf2_org on May 18, 2011, 02:16:14 PM

Quote from: Gavin Andresen on May 18, 2011, 01:37:14 PM

Quote from: MoonShadow on May 18, 2011, 01:28:33 PM

Then a "stealth" client is needed, that functions as a dark node unless specificly commanded to connect to a particular peer, or accept a particular peer's requests. In fact, I want this client, portable on a thumbdrive.

That is exactly what -connect does (if I recall correctly; you might need -connect and -nolisten together).

Correct. -nolisten disables incoming, and -connect restricts outgoing to -connect-provided whitelist.

Perfect. Thanks guys!

xf2_org

member

Activity: 98

Merit: 13

Quote from: Gavin Andresen on May 18, 2011, 01:37:14 PM

Quote from: MoonShadow on May 18, 2011, 01:28:33 PM

Then a "stealth" client is needed, that functions as a dark node unless specificly commanded to connect to a particular peer, or accept a particular peer's requests. In fact, I want this client, portable on a thumbdrive.

That is exactly what -connect does (if I recall correctly; you might need -connect and -nolisten together).

Correct. -nolisten disables incoming, and -connect restricts outgoing to -connect-provided whitelist.

Gavin Andresen

legendary

Activity: 1652

Merit: 2311

Chief Scientist

Quote from: MoonShadow on May 18, 2011, 01:28:33 PM

Then a "stealth" client is needed, that functions as a dark node unless specificly commanded to connect to a particular peer, or accept a particular peer's requests. In fact, I want this client, portable on a thumbdrive.

That is exactly what -connect does (if I recall correctly; you might need -connect and -nolisten together).

MoonShadow

legendary

Activity: 1708

Merit: 1010

Quote from: Matt Corallo on May 18, 2011, 01:25:24 PM

Quote from: MoonShadow on May 18, 2011, 01:21:48 PM

Search the forum for the "shy" client. Someone has already modified the vanilla client to only accept approved connections and never announce it's own IP address.

That is not at all what the "shy" patch does. The shy patch only sends its version number to clients it connects to after they send it theirs. It still connects to IRC, still attempts to make the same 8 outgoing connections to random nodes as every other client, and still listens for incoming connections. The only goal here is to make bitcoin nodes slightly less DDoS-able. Also, shy is in git, and I believe also in 0.3.21.

Thanks for the correction. Then a "stealth" client is needed, that functions as a dark node unless specificly commanded to connect to a particular peer, or accept a particular peer's requests. In fact, I want this client, portable on a thumbdrive.

Matt Corallo

hero member

Activity: 755

Merit: 515

Quote from: MoonShadow on May 18, 2011, 01:21:48 PM

Search the forum for the "shy" client. Someone has already modified the vanilla client to only accept approved connections and never announce it's own IP address.

That is not at all what the "shy" patch does. The shy patch only sends its version number to clients it connects to after they send it theirs. It still connects to IRC, still attempts to make the same 8 outgoing connections to random nodes as every other client, and still listens for incoming connections. The only goal here is to make bitcoin nodes slightly less DDoS-able. Also, shy is in git, and I believe also in 0.3.21.

MoonShadow

legendary

Activity: 1708

Merit: 1010

Search the forum for the "shy" client. Someone has already modified the vanilla client to only accept approved connections and never announce it's own IP address.

Matt Corallo

hero member

Activity: 755

Merit: 515

Quote from: syn on May 18, 2011, 11:01:33 AM

Is there a way to change a config parameter in bitcoind to give it a limited (trusted) set of hosts it should communicate with? I've looked around and didn't ind anything obvious.

The -connect parameter limits bitcoin to connect only to the node you specify, you can add several -connect's to connect to several nodes.

syn

newbie

Activity: 25

Merit: 0

Is there a way to change a config parameter in bitcoind to give it a limited (trusted) set of hosts it should communicate with? I've looked around and didn't ind anything obvious.

Topic: restricting access to nodes bitcoind talks to (Read 1228 times)