View Issue Details

IDProjectCategoryView StatusLast Update
0002993GNUnetnamestore servicepublic2013-12-24 20:54
ReporterChristian Grothoff Assigned ToChristian Grothoff  
PriorityurgentSeverityblockReproducibilityN/A
Status closedResolutionfixed 
Product VersionGit master 
Target Version0.10.0Fixed in Version0.10.0 
Summary0002993: namestore fails to consider our own records during standard (encyrpted) lookup
DescriptionWe currently do not make the records that are indexed under private keys available under the respective public keys. However, our resolver will only look under the public keys. Thus, we'd miss the records in our own zone and resolutions won't work. As some of our own zone's records may be private, we would not even find those in the DHT (which would be inefficient anyway).

So the namestore should always convert all "private" records to "public" records (with infinite expiration time) and keep the two sets synchronized.
TagsNo tags attached.

Activities

Christian Grothoff

2013-08-15 12:26

manager   ~0007377

Fixed in SVN 28645 (by duplicating records from our private zone into the block zone whenever they are created).

Issue History

Date Modified Username Field Change
2013-08-13 21:19 Christian Grothoff New Issue
2013-08-13 21:49 Christian Grothoff Status new => confirmed
2013-08-14 22:01 Christian Grothoff Priority normal => urgent
2013-08-15 12:09 Christian Grothoff Assigned To => Christian Grothoff
2013-08-15 12:09 Christian Grothoff Status confirmed => assigned
2013-08-15 12:26 Christian Grothoff Note Added: 0007377
2013-08-15 12:26 Christian Grothoff Status assigned => resolved
2013-08-15 12:26 Christian Grothoff Fixed in Version => 0.10.0
2013-08-15 12:26 Christian Grothoff Resolution open => fixed
2013-10-02 13:56 Christian Grothoff Category namestore => namestore service
2013-12-24 20:54 Christian Grothoff Status resolved => closed