[Nfd-dev] [EXT]Re: Try NDNCERT (based on Interest-Data exchange) and get an NDN certificate today

[Zhiyi Zhang]

With the current NDNCERT implementation, the certificate will still be
fetched and installed on the local keychain.
However, you are right in the sense that, the certificate cannot be fetched
asynchronously after the NDNCERT client command ends.

BTW, shouldn't Repe be installed on all testbed nodes through the operator?

Best,
Zhiyi

On Wed, Jan 20, 2021 at 8:08 PM Junxiao Shi <shijunxiao at email.arizona.edu>
wrote:

> Hi Zhiyi
>
> It doesn't make sense to run NDNCERT without a repo.
>
> 1. CA profile is not retrievable, so that client cannot initiate.
> 2. Issued certificate is not retrievable, so that client cannot finish.
>
> Yours, Junxiao
>
> On Wed, Jan 20, 2021, 22:38 Zhiyi Zhang <zhiyi at cs.ucla.edu> wrote:
>
>> *External Email*
>> Yeah. I found the repo is not running on the Suns: ERROR: Cannot publish
>> certificate to repo-ng (Connection refused)
>>
>> @Lixia do you know who should I contact to deploy the repo? and which
>> repo should be used?
>>
>> I just bring back the NDNCERT without the parameter to publish to the
>> repo. After people figure out the repo deployment, I will update the
>> parameter used in NDNCERT service.
>>
>> Best,
>> Zhiyi
>>
>> On Wed, Jan 20, 2021 at 11:11 AM Junxiao Shi <
>> shijunxiao at email.arizona.edu> wrote:
>>
>>> Hi Zhiyi
>>>
>>> As you mentioned on the 2021-01-15 NFD call, you have updated the
>>> deployment to use 2019 Naming Convention.
>>> However, I'm now unable to retrieve the CA profile - the CA is not
>>> responding at all.
>>>
>>> $ ndnpeek -Pf /ndn/CA/INFO/32=metadata
>>> $ echo $?
>>> 3
>>>
>>> Wireshark and NFD counters indicate that the Interest has arrived on
>>> suns.cs.ucla.edu, but there's no response.
>>>
>>> Yours, Junxiao
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20210120/7a0c2e30/attachment-0001.html>