View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002993GNUnetnamestore servicepublic2013-08-13 19:192013-12-24 19:54
ReporterChristian Grothoff Assigned ToChristian Grothoff Due Date
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 10: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 ModifiedUsernameFieldChange
2013-08-13 19:19Christian GrothoffNew Issue
2013-08-13 19:49Christian GrothoffStatusnew => confirmed
2013-08-14 20:01Christian GrothoffPrioritynormal => urgent
2013-08-15 10:09Christian GrothoffAssigned To => Christian Grothoff
2013-08-15 10:09Christian GrothoffStatusconfirmed => assigned
2013-08-15 10:26Christian GrothoffNote Added: 0007377
2013-08-15 10:26Christian GrothoffStatusassigned => resolved
2013-08-15 10:26Christian GrothoffFixed in Version => 0.10.0
2013-08-15 10:26Christian GrothoffResolutionopen => fixed
2013-10-02 11:56Christian GrothoffCategorynamestore => namestore service
2013-12-24 19:54Christian GrothoffStatusresolved => closed