Feature #3776
Updated by Junxiao Shi over 7 years ago
When a non-existent identity/key/certificate What is specified to be set as default in `ndnsec-set-default`, it is silently created. In most cases, the operator wants to set an existing identity/key/certificate as the default rather than creating a new one, because creating new identity as default is already supported by `ndnsec-keygen` command. purpose for supporting this behavior? `ndnsec-set-default` <pre> $ ndnsec list /ndn/edu/ucla/remap/jburke * /ndn/edu/ucla/jburke /ndn/edu/jburke/golem $ ndnsec set-default /dish/soap [Silence...] $ ndnsec list * /dish/soap <= not available /ndn/edu/ucla/jburke/golem /ndn/edu/ucla/remap/jburke /ndn/edu/ucla/jburke </pre> Even if identities without certs can be added, I would suggest that set-default should print a warning warn or fail if new identity/key/certificate is being created, to alert the operator about possible human error. cert isn't available.