Actions
Bug #3469
closedndnsec-op-tool broken
Start date:
02/23/2016
Due date:
% Done:
100%
Estimated time:
0.10 h
Description
To reproduce the problem:
# if default identity/certificate doesn't exist
# ndnsec-keygen /tmp/1111 | ndnsec-install-cert -
echo "Hello, world" | ndnsec-op-tool sign
Expected: binary output of SignatureValue TLV block
Actual:
ERROR: (Block::wire) Underlying wire buffer is empty
Updated by Junxiao Shi over 8 years ago
- Estimated time changed from 0.10 h to 0.10 h
Can you explain what is ndnsec-op-tool
? It doesn't have a manpage, and help message is very limited.
Updated by Alex Afanasyev over 8 years ago
- Estimated time changed from 0.10 h to 0.10 h
This is just a small tool with limited scope (used by ndncert operator tools)
Updated by Junxiao Shi over 8 years ago
- Estimated time changed from 0.10 h to 0.10 h
note-1 asks for what is ndnsec-op-tool
. note-2 describes where is ndnsec-op-tool
used, and does not answer note-1 question.
Updated by Alex Afanasyev over 8 years ago
- Estimated time changed from 0.10 h to 0.10 h
It is a tool to sign data from the standard input and output SignatureValue block
Updated by Junxiao Shi over 8 years ago
- Estimated time changed from 0.10 h to 0.10 h
Pushing the question further:
- Why is this named
ndnsec-op-tool
instead ofndnsec-sign
? - If it's for ndncert, why not move it to ndncert repository? (OSX keychain limitation is not a factor because testbed gateway routers are not OSX)
Updated by Alex Afanasyev over 8 years ago
- Estimated time changed from 0.10 h to 0.10 h
This can be a separate issue. Right now, I want to fix the bug that is preventing ndnop-process-requests
from working. Please don't stall this.
Updated by Alex Afanasyev over 8 years ago
- Status changed from Code review to Closed
- Estimated time changed from 0.10 h to 0.10 h
Actions