Project

General

Profile

Bug #4202

ndnsec cert-gen: subject-name is missing

Added by Luca Keidel over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
High
Category:
Security
Target version:
Start date:
07/24/2017
Due date:
% Done:

100%

Estimated time:

Description

**When I try to generate a certificate by signing a signing request using the ndnsec command line tools, I get the following error: ERROR: subject name must be specified.

Steps to reproduce:

$ ndnsec key-gen /another_identity
  [...]
$ ndnsec key-gen /identity
  [...]
$ ndnsec sign-req /identity > identity.signreq
$ ndnsec cert-gen -s /another_identity -i ai identity.signreq
ERROR: subject name must be specified

General Usage
[...]

Apparently, this error is caused by the check in tools/ndnsec/cert-gen.cpp which checks for a subject-info option. However, no such option is defined in the available options of the cert-gen command and neither is it used later on.


Related issues

Blocks NFD - Task #4275: Release 0.6.0ClosedAlex Afanasyev

Actions
#1

Updated by Junxiao Shi over 3 years ago

  • Subject changed from ndnsec command line tools: subject-name check in to ndnsec cert-gen: subject-name is missing
  • Description updated (diff)
  • Category set to Security
  • Assignee set to Alex Afanasyev
  • Priority changed from Normal to High
  • Target version set to v0.6

The subject-name option is deleted in ndn-cxx:commit:35109a19d048365fda0a5efdb7c1525404a212a5, but the check was forgotten.
I believe it's being replaced by -I option, but what's the equivalent syntax? What token do I put in front of the value?

#2

Updated by Alex Afanasyev over 3 years ago

  • Status changed from New to In Progress

In addition to incorrect error, cert-gen doesn't properly encode additional information: the code processes it, but doesn't actually adds to the certificate.

#3

Updated by Alex Afanasyev over 3 years ago

  • Status changed from In Progress to Code review
  • % Done changed from 0 to 100
#4

Updated by Junxiao Shi over 3 years ago

#5

Updated by Junxiao Shi over 3 years ago

  • Description updated (diff)
  • Status changed from Code review to Closed

I confirm the bug has been fixed.

Also available in: Atom PDF