<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class=""><br class="">
</div>
Haitao,
<div class=""><br class="">
</div>
<div class="">I will see what has changed. </div>
<div class=""><br class="">
</div>
<div class="">John</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jul 30, 2017, at 10:38 PM, Haitao Zhang <<a href="mailto:zhtaoxiang@gmail.com" class="">zhtaoxiang@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div style="font-size:12.8px" class="">Hi dev team,</div>
<div style="font-size:12.8px" class=""><br class="">
</div>
<div style="font-size:12.8px" class="">Previously, I used this tool <a href="https://github.com/yoursunny/ndn6-tools/blob/master/remote-register-prefix.md" target="_blank" class="">remote-register-prefix</a> (<wbr class="">on Linux machine) and use interest
"/localhop/nfd/rib/register/<<wbr class="">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?</div>
<div style="font-size:12.8px" class=""><br class="">
</div>
<div style="font-size:12.8px" class="">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".</div>
<div style="font-size:12.8px" class=""><br class="">
</div>
<div style="font-size:12.8px" class="">Correct me if I am wrong. Thank you for your help in advance!</div>
<br class="">
<div class="">
<div class="gmail_signature">
<div dir="ltr" class="">
<div class="">Best,<br class="">
</div>
-Haitao<br class="">
</div>
</div>
</div>
</div>
_______________________________________________<br class="">
Nfd-dev mailing list<br class="">
<a href="mailto:Nfd-dev@lists.cs.ucla.edu" class="">Nfd-dev@lists.cs.ucla.edu</a><br class="">
http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev<br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>