[Ndn-interest] [Question] What's the purpose of the NFD's default signing key?
aa at CS.UCLA.EDU
Thu Feb 23 08:07:48 PST 2017
> On Feb 23, 2017, at 5:58 AM, Lan Wang (lanwang) <lanwang at memphis.edu> wrote:
> Thank you for the information. Just a few clarification questions:
>> On Feb 22, 2017, at 11:22 PM, Alex Afanasyev <aa at cs.ucla.edu <mailto:aa at cs.ucla.edu>> wrote:
>> As Lan pointed out already,  is very old guide for NDNx codebase and many statements there don't apply to NFD.
>> The "default" key that is created by nfd-start is only used to sign responses for NFD management requests and commands and current tools don't do validation of the responses. The applications and tools that want to register prefixes with NFD, they need to use keys that are authorized by NFD for this operation.
> Why and how do applications and tools get keys authorized by NFD? Does every application need to do this?
This is deployment issue. If NFD uses strict checking for prefix registration signatures, then all applications that want to publish would need to have keys. This either local trust anchor CA needs to issue certificates for local apps or keys of applications need to be explicitly trusted by NFD.
>> In our default deployment, we have a very relaxed policy to allow any local registrations, which can be tied up in nfd.conf. The default policy for "remote" registration (using /localhop/nfd) is to deny all and on our testbed nodes we require commands to be signed by a valid NDN Testbed certificate.
>>> On Feb 21, 2017, at 10:55 AM, Lei Pi <lpi at memphis.edu <mailto:lpi at memphis.edu>> wrote:
>>> While reading documents on redmine, I found myself confused with the "Using registerPrefix with NFD" part of article "Application Development Documentation / Guides". The original text of the article goes as follows:
>>> >>> When you install NFD, it installs a default signing key on your system. For registerPrefix to create a signed command interest using this default signing key, your application needs to use the default KeyChain constructor and call setCommandSigningInfo so that the Face can sign the command interest created by registerPrefix
>>> But when an application sends out a command interest, the recipient should check if the interest's signing key is finally signed by an administrator's signing key in order to reject unauthorized commands .
>>> So what's the purpose of the NFD's default signing key? Why should the app use this key to initialize its identity ? Note the NFD's default signing key is not signed by anyone .
>>> If it is also for defend ing against unauthorized command interests, then any local app, including possible malwares, can also use this key to sign their interest by simply using the default keychain.
>>> If not, what other purpose could it be?
>>>  https://redmine.named-data.net/projects/application-development-documentation-guides/wiki/Using_Client_Libraries_with_NDNx_vs_NDNx-TLV_vs_NFD#Using-registerPrefix-with-NFD <https://redmine.named-data.net/projects/application-development-documentation-guides/wiki/Using_Client_Libraries_with_NDNx_vs_NDNx-TLV_vs_NFD#Using-registerPrefix-with-NFD>
>>>  https://github.com/named-data/NFD/blob/master/tools/nfd-start.sh#L42 <https://github.com/named-data/NFD/blob/master/tools/nfd-start.sh#L42>
>>> Thank you.
>>> Lei Pi
>>> University of Memphis
>>> Ndn-interest mailing list
>>> Ndn-interest at lists.cs.ucla.edu <mailto:Ndn-interest at lists.cs.ucla.edu>
>>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest <http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest>
>> Ndn-interest mailing list
>> Ndn-interest at lists.cs.ucla.edu <mailto:Ndn-interest at lists.cs.ucla.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ndn-interest