You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting the sample applications, e.g., app2 frequently causes prefix registration errors. To reproduce the identical environment, spin-up a VM using the following Vagrantfile:
My profound apologies. I neglected to push the patch to ndn-cxx that prevents this. It is the cxx-register-bug.patch which is now in the NDNpatches repo. DCT is setting up multiple syncps collections and attempting to register the prefixes. The 1 ms restriction is what causes this issue.
I would like to highlight that this patch allows for potential replay attacks and should be seen as temporary fix only. Thanks for pointing to the error's cause.
Okay. Note that the original code does not actually prevent replay (identical Interests) but limits the number of Command Interests to one per millisecond as a sort of proxy for replay prevention code.
Starting the sample applications, e.g.,
app2
frequently causes prefix registration errors. To reproduce the identical environment, spin-up a VM using the following Vagrantfile:The Vagrantfile already creates three identities for the operators "Alice", "Bob", and "Cathy" in the folder
DCT/examples/mbps/
.After starting NFD, repeatedly starting
app2
causes the following error:The text was updated successfully, but these errors were encountered: