> > Should a node wish to unrequest some data, it sends an unrequest message > which contains the unhashed version of the unrequest key, thus verifying > the validity of the unrequest. On receiving such an unrequest a node > attempts, to whatever extent possible, to undo the effect of the > original datarequest and its resulting datareply. It then forwards the > unrequest on to the next node in the chain (unless it is the original > source of the datareply).
You would still need to invalidate the message-memory unrequest key after processing it, or you could perform a replay attack, by requesting a document, then repeatedly unrequesting it. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20000518/a661d407/attachment.pgp>
