From 492356d11b87dc410482fcab603934ef5da585e3 Mon Sep 17 00:00:00 2001
From: eyedeekay <idk@mulder>
Date: Thu, 26 Oct 2023 14:05:14 -0400
Subject: [PATCH] Router: Remove comment
---
.../router/networkdb/HandleDatabaseLookupMessageJob.java | 6 ------
1 file changed, 6 deletions(-)
diff --git a/router/java/src/net/i2p/router/networkdb/HandleDatabaseLookupMessageJob.java b/router/java/src/net/i2p/router/networkdb/HandleDatabaseLookupMessageJob.java
index 09f0f91cb0..3892c4291d 100644
--- a/router/java/src/net/i2p/router/networkdb/HandleDatabaseLookupMessageJob.java
+++ b/router/java/src/net/i2p/router/networkdb/HandleDatabaseLookupMessageJob.java
@@ -151,12 +151,6 @@ public class HandleDatabaseLookupMessageJob extends JobImpl {
CLOSENESS_THRESHOLD, null);
if (weAreClosest(closestHashes)) {
// It's in our keyspace, so give it to them
- // there is a slight chance that there is also a multihomed router in our cache at the
- // same time we are closest to our locally published leaseSet. That means there is a slight
- // chance an attacker can send a least as a store which goes into the multihome cache, then
- // fetch back a locally-created, locally-published leaseset. BUT, if we always publish a
- // multihomed leaseset even if we are closest to the local, we never send it out if a potential
- // multihome is found in the cache.
if (_log.shouldLog(Log.INFO))
_log.info("We have local LS " + searchKey + ", answering query, in our keyspace");
getContext().statManager().addRateData("netDb.lookupsMatchedLocalClosest", 1);
--
GitLab