aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--src/nse/nse.h22
1 files changed, 0 insertions, 22 deletions
diff --git a/src/nse/nse.h b/src/nse/nse.h
index 245bd4ca7..f0a914488 100644
--- a/src/nse/nse.h
+++ b/src/nse/nse.h
@@ -66,28 +66,6 @@ struct GNUNET_NSE_ClientMessage
66 * Network size estimate reply; sent when "this" 66 * Network size estimate reply; sent when "this"
67 * peer's timer has run out before receiving a 67 * peer's timer has run out before receiving a
68 * valid reply from another peer. 68 * valid reply from another peer.
69 *
70 * FIXME: Is this the right way to do this?
71 * I think we need to include both the public
72 * key and the timestamp signed by the private
73 * key. This way a recipient
74 * can verify that the peer at least generated
75 * the public/private key pair, and that the
76 * timestamp matches what the current peer
77 * believes it should be. The receiving peer
78 * would then check whether the XOR of the peer
79 * identity and the timestamp is within a
80 * reasonable range of the current time
81 * (+/- N seconds). If a closer message which
82 * also verifies hasn't been received (or this
83 * message is a duplicate), the peer
84 * calculates the size estimate and forwards
85 * the request to all other peers.
86 *
87 * Hmm... Is it enought to *just* send the peer
88 * identity? Obviously this is smaller, but it
89 * doesn't allow us to verify that the
90 * public/private key pair were generated, right?
91 */ 69 */
92struct GNUNET_NSE_FloodMessage 70struct GNUNET_NSE_FloodMessage
93{ 71{