Project

General

Profile

Actions
Copy link

Bug #2052

closed

ndnsec doesn't correctly infer prefix before KEY

Added by Alex Afanasyev over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
High
Assignee:
Yingdi Yu
Category:
Security
Target version:
v0.3
Start date:
Due date:
% Done:

100%

Estimated time:

Description

Somehow, ndnsec doesn't perform proper inference for the prefix before KEY based on signing identity.

Say:

  • signing identity: /alex
  • request for identity: /alex/hello/world (name in request: /alex/hello/world/KEY/ksk-1412971757948/ID-CERT/%00%00%01H%FB%AE%01%CD)

Run:

ndnsec-cert-gen -N 'test' -s /alex -r -

Expected certificate name:

/alex/KEY/hello/world/ksk-1412971757948/ID-CERT/%00%00%01H%FB%B0P%7E

Actual certificate name:

/KEY/alex/hello/world/ksk-1412971757948/ID-CERT/%00%00%01H%FB%B0P%7E

The current workaround is to add --cert-prefix=/alex, but this shouldn't be the case.

Related issues 1 (0 open — 1 closed)

Related to ndn-cxx - Task #1659: Allow user to explicitly specify the cert name prefix in ndnsec-certgenClosedYingdi Yu06/12/2014

Actions
Actions
Copy link
 #1

Updated by Alex Afanasyev over 9 years ago

  • Related to Task #1659: Allow user to explicitly specify the cert name prefix in ndnsec-certgen added
Actions
Copy link
 #2

Updated by Yingdi Yu over 9 years ago

  • Status changed from New to Code review
  • % Done changed from 0 to 100
Actions
Copy link
 #3

Updated by Junxiao Shi over 9 years ago

  • Tracker changed from Task to Bug
Actions
Copy link
 #4

Updated by Junxiao Shi over 9 years ago

  • Status changed from Code review to Closed
Actions
Copy link

Also available in: Atom PDF