[Nfd-dev] ndnsec import asks for passphrase twice

Alex Afanasyev aa at CS.UCLA.EDU
Tue Jun 7 10:52:56 PDT 2016


> On Jun 6, 2016, at 7:07 PM, Junxiao Shi <shijunxiao at email.arizona.edu> wrote:
> 
> Dear folks
> 
> ndnsec import command is used to import a previously exported private key.
> The private key is protected by a passphrase so the operator is prompted to enter it.
> I notice that this command, similar to ndnsec export, asks for the passphrase twice.
> 
> vagrant at m0212:~$ ndnsec import -p mykey.ndnkey
> Passphrase for the private key:
> Confirm:
> 
> Is there a particular design rationale behind this, or is it a UX bug?

I also noticed this.  It is a UX bug.

---
Alex

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160607/587e8c11/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160607/587e8c11/attachment.bin>


More information about the Nfd-dev mailing list