View Issue Details

IDProjectCategoryView StatusLast Update
0003310GNUnetDHT servicepublic2018-06-07 01:14
ReporterBart Polot Assigned To 
Status confirmedResolutionopen 
Product VersionGit master 
Summary0003310: DHT should have a randomization option
DescriptionDHT should have a configuration option to indicate the minimum/maximum amounts of randomization used for keys, and a fixed hardcoded limit (64 bits).
Additional InformationThe hardcoded limit is in place so requests with different randomization "sizes" are compatible with each other.
- A peer that decides to do a PUT with 16 bits randomized can use a value of up to 0x000000000000FFFF to hash with the original ID.
- A peer that decided to do a GET with 8 bits randomized withh use a value of up to 0x00000000000000FF to hash with to original ID.
- If the PUT was done with a value of 0x0000000000000000 to 0x00000000000000FF, the GET has a chance to be found. If the PUT was done with a value of 0x0000000000000100 to 0x000000000000FFFF the GET won't succeed.

If the PUT was done with a hash value from 0x0000 to 0xFFFF, a GET for a hash value from 0x00 to 0xFF, the GET would never succeed. This is because hashing 0x00FF and 0xFF result in different values.
TagsNo tags attached.


child of 0002454 confirmed key randomization via RO_BART is not implemented 


There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2014-02-07 15:01 Bart Polot New Issue
2014-02-07 15:01 Bart Polot Status new => assigned
2014-02-07 15:01 Bart Polot Assigned To => Bart Polot
2014-02-07 15:01 Bart Polot Relationship added child of 0002454
2014-02-07 15:27 Bart Polot Additional Information Updated
2014-04-11 15:15 Christian Grothoff Product Version => Git master
2014-04-11 15:15 Christian Grothoff Target Version => 0.11.0
2018-06-07 00:30 Christian Grothoff Target Version 0.11.0 =>
2018-06-07 01:14 Christian Grothoff Assigned To Bart Polot =>
2018-06-07 01:14 Christian Grothoff Status assigned => confirmed