[Nfd-dev] Push the Deployment of NDNCERT

[Junxiao Shi]

Hi Yufeng

1. Has the hardware change happened, or not yet?
2. If it has happened, when did it happen?
3. What OS is running on the current hardware?
4. What error message do you receive when you attempt to start repo-ng?

Before you ask:
Although repo-ng is deprecated, it's the only choice to serve certificates.
JonnyKong's repo cannot serve certificates because it re-signs every packet
<https://github.com/JonnyKong/NDN-Repo/blob/47b62cbab776a4b6480c741d8b6c4d09ba96a2a8/src/handle/read_handle.py#L33>
and
cannot preserve the signature placed by the CA.

Yours, Junxiao

On Fri, Nov 29, 2019 at 3:20 PM Yufeng Scott Zhang <yufeng at ucla.edu> wrote:

> Hi Junxiao,
>
> I believe it used to run on spurs, and the issue is probably caused by the
> migration from old spurs to the new one.
>
> On Fri, Nov 29, 2019 at 12:16 Junxiao Shi <shijunxiao at email.arizona.edu>
> wrote:
>
>> Dear folks
>>
>> I think the problem is that repo-ng is not running, as I do not see a
>> /localhost/repo-ng route.
>> Since ndncert depends on both NFD and repo-ng, its systemd unit file
>> should declare dependency as such, and restart ndncert whenever either of
>> these dependencies is restarted.
>>
>> Yours, Junxiao
>>
>> On Fri, Nov 29, 2019 at 3:07 AM Yufeng Zhang <yufeng at ucla.edu> wrote:
>>
>>> I think even though the certificate can be issued, it doesn’t
>>> necessarily mean that the certificate is inserted into the repo.
>>>
>>> Besides, the status page is http://spurs.cs.ucla.edu/
>>>
>>> > On Nov 29, 2019, at 12:02 AM, Hunter Dellaverson <
>>> hdellaverson at gmail.com> wrote:
>>> >
>>> > Seems like the flags were correct. I know that we're moving to a new
>>> spurs server, so I wonder if this is related.
>>> >
>>> > Moreover, I think I'm a bit confused: I was just able to request a new
>>> certificate, and could query spurs for both pending and issued certificates
>>> successfully (using the ndncert-ca-status command that you installed,
>>> Yufeng).
>>> >
>>> > P.S. Could you direct me to the spurs status page? Wasn't aware of it.
>>> >
>>> > On Thu, Nov 28, 2019, 23:45 Yufeng Zhang <yufeng at ucla.edu> wrote:
>>> > Hi Hunter,
>>> >
>>> > Did we use the correct repo flag when starting NDNCERT?
>>> >
>>> > The flags are: -r -H 127.0.0.1 -P 7376
>>> >
>>> > Please let me know, thanks!
>>> >
>>> >
>>> > > On Nov 28, 2019, at 8:22 PM, Junxiao Shi <
>>> shijunxiao at email.arizona.edu> wrote:
>>> > >
>>> > > Hi Yufeng and Hunter
>>> > >
>>> > > I notice that NDNCERT CA was restarted at 2019-11-29 03:38:33 UTC+0,
>>> and then repo is not working properly. Neither existing certificates nor
>>> new certificates is reachable, and their prefix registrations are absent on
>>> spurs status page.
>>> > >
>>> > > Yours, Junxiao
>>> >
>>> > <spursFlags.png>
>>>
>>> --
> *Kindly Regards, *
> Yufeng Zhang
> Henry Samueli School of Engineering and Applied Science
> University of California, Los Angeles '22
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20191129/37e2f06a/attachment.html>