[Nfd-dev] Question about localhop security policy of NDN testbed nodes

[Haitao Zhang]

Hi dev team,

Previously, I used this tool remote-register-prefix
<https://github.com/yoursunny/ndn6-tools/blob/master/remote-register-prefix.md>
 (on Linux machine) and use interest "/localhop/nfd/rib/register/<control
parameter>" (on Android) to register back route on NDN testbed edge router,
the signing identity/key/certificate (/org/openmhealth/<user-id>) was
issued by NDNFit trust anchor (/org/openmhealth); however, it doesn't work
any more. I believe it's because the localhop security policy was changed
(i.e., localhop_security field of nfd.conf was changed), so only interests
signed by identity/key/certificate that can be tracked back to NDN testbed
trust anchor could register back route on NDN testbed successfully. It this
true, or is there another reason?

If my suspicion is true, could you help to manually issue a cert to NDNFit
trust anchor using NDN testbed trust anchor (or could you grant me the
privilege to do so), so that my remote register interest can be verified? I
want to manually do this because NDNFit trust anchor was not bound with an
email. Another option is to replace NDNFit trust anchor with an
identity/key/certificate that is bound with an email (we can create a new
email account). I prefer the former choice as we want to keep the identity
name "/org/openmhealth".

Correct me if I am wrong. Thank you for your help in advance!

Best,
-Haitao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20170730/5e60e640/attachment-0001.html>