View Issue Details

IDProjectCategoryView StatusLast Update
0003481GNUnetDHT servicepublic2018-06-06 22:51
ReporterChristian Grothoff Assigned ToDue Date
PrioritylowSeverityfeatureReproducibilityN/A
Status confirmedResolutionopen 
Product VersionGit master 
Summary0003481: DHT monitor should allow dropping / ignoring of requests
DescriptionIn the P2P course, it was discussed (for Scribe) that a feature for the monitor to drop an observed request (force it not to be routed further or stored) can be desirable. This could *also* be used to simulate malicious peers. While the result would not be strictly a 'monitor' anymore, clearly the monitor API would be the right place to do this. For example, the callback could simply indicate to 'continue forwarding' or 'drop/ignore' by return value.

A main change in the service would of course be that we'd now have to wait for 'all' monitors to give us that return value via IPC before continuing to process a request. However, as we usually might not have a monitor, this might be cheap. We might also want to allow monitors to register only for certain block types to keep the cost down even more.
TagsNo tags attached.

Relationships

has duplicate 0003509 confirmedSree Harsha Totakura Monitoring API should enable dropping DHT messages 

Activities

There are no notes attached to this issue.

Issue History

Date ModifiedUsernameFieldChange
2014-07-02 15:38Christian GrothoffNew Issue
2014-07-02 15:38Christian GrothoffStatusnew => assigned
2014-07-02 15:38Christian GrothoffAssigned To => Bart Polot
2014-08-06 09:41Christian GrothoffRelationship addedhas duplicate 0003509
2018-06-06 22:51Christian GrothoffAssigned ToBart Polot =>
2018-06-06 22:51Christian GrothoffPrioritynormal => low
2018-06-06 22:51Christian GrothoffStatusassigned => confirmed