Project

General

Profile

Actions
Copy link

Bug #1889

closed

NFD/NRD startup fails in tpm=file mode if some PIB entries are stored in osx-keychain TPM

Added by Jeff Burke over 10 years ago. Updated over 10 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Security
Target version:
-
Start date:
08/18/2014
Due date:
% Done:

0%

Estimated time:

Description

If the PIB holds entries held in the osx-keychain TPM, but NRD/NFD are started with tpm=file in client.conf, startup fails.

Steps to reproduce:

  1. rm -rf ~/.ndn/ndnsec-* [Optional!]
  2. Set tpm=file in client.conf
  3. Run nfd-start, default identity will be created. Then, nfd-stop.
  4. Switch to tpm=osx-keychain in client.conf.
  5. Run ndnsec-keygen /localhost/foo | ndnsec-install-cert -
  6. Set tpm=file in client.conf
  7. Run nfd-start, should fail as follows: 1408410473.015812 FATAL: [NFD] private key doesn't exists 1408410475.013264 INFO: [RibManager] Listening on: /localhost/nfd/rib 1408410475.015285 FATAL: [NRD] private key doesn't exists
  8. Run sqlite3 ~/.ndn/ndnsec-public-info.db 'delete from Identity where identity_name="/localhost/foo";'
  9. Run nfd-start, should work fine.
Actions
Copy link

Also available in: Atom PDF