NFD » ndn-tools

Generally speaking, PIB should sign its reply using a strong signature. However, some platforms (such as RaspberryPI) have constrained power and apps on the system may assume that NFD can be trusted to provide the data returned by PIB if NFD honestly performs prefix registration authentication and reject unsolicited data packet. In this case, it would be helpful to ask PIB to use sha256 digest as signature to reduce the overhead of signing.

An example of the proposed new configuration file should look like this:

pib-dir /usr/local/etc/ndn/pib              ; path to the db file
security 
{
  status on                                 ; strong sig is used when status is on, sha256 is used when status is off.
  tpm-dir /usr/local/var/ndn/pib/tpm        ; path to the tpm
  pib-root /usr/local/etc/ndn/pib/root.cert ; path to the pib root cert (trust anchor of pib service)
}