Ignore getaddr messages on Outbound connections.
The only time when a client sends a "getaddr" message is when he esatblishes an Outbound connection (see ProcessMessage() in src/main.cpp). Another bitcoin client is expected to receive a "getaddr" message only on Inbound connection. Ignoring "gettaddr" requests on Outbound connections can resolve potential privacy issues (and as was said such request normally do not happen anyway).
This commit is contained in:
parent
fb6140b54b
commit
dca799e1db
1 changed files with 6 additions and 1 deletions
|
@ -4008,7 +4008,12 @@ bool static ProcessMessage(CNode* pfrom, string strCommand, CDataStream& vRecv,
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
||||||
else if (strCommand == "getaddr")
|
// This asymmetric behavior for inbound and outbound connections was introduced
|
||||||
|
// to prevent a fingerprinting attack: an attacker can send specific fake addresses
|
||||||
|
// to users' AddrMan and later request them by sending getaddr messages.
|
||||||
|
// Making users (which are behind NAT and can only make outgoing connections) ignore
|
||||||
|
// getaddr message mitigates the attack.
|
||||||
|
else if ((strCommand == "getaddr") && (pfrom->fInbound))
|
||||||
{
|
{
|
||||||
pfrom->vAddrToSend.clear();
|
pfrom->vAddrToSend.clear();
|
||||||
vector<CAddress> vAddr = addrman.GetAddr();
|
vector<CAddress> vAddr = addrman.GetAddr();
|
||||||
|
|
Loading…
Reference in a new issue