[Nfd-dev] Question on error - `/localhost/operator` does not have a default certificate’

[Adil Hidayat Bin Rosli]

Hi Junxiao,

Thank you very much for your reply. It would be really great if you could help to build the packages for Buster. I current use both Raspberry Pi 2 and 3. Also I have several Raspberry Pi 4 with me.

Best regards
Adil
On 25 Aug 2019, 4:56 PM +0800, Junxiao Shi <shijunxiao at email.arizona.edu>, wrote:
> Hi Adil
>
> In Debian/Ubuntu systems, you are supposed to use .deb packages.
> I currently publish NDN packages for Debian/Raspbian Stretch on https://dl.bintray.com/yoursunny/named-data/ . They are built with this script: https://github.com/yoursunny/docker-nfd/blob/84fe1469808cee601afde7d21e220e276d01ae9f/debuild.sh .
> If you need packages for Buster, I can build them for you next week. Do you need it for Pi2 or Pi3? Optimization flags are different.
>
> Yours, Junxiao
>
> > On Sat, Aug 24, 2019 at 10:49 PM Adil Hidayat Bin Rosli via Nfd-dev <nfd-dev at lists.cs.ucla.edu> wrote:
> > > Hi all,
> > >
> > > I have a question regarding some certificate related errors that I got when starting the nfd (issuing the ‘nfd-start’).
> > >
> > > I am currently using a Raspberry Pi 2/3. Below are details of my OS:
> > >
> > > 'lsb_release -a' output:
> > >  No LSB modules are available.
> > >  Distributor ID: Raspbian
> > >  Description: Raspbian GNU/Linux 10 (buster)
> > >  Release: 10
> > >  Codename: buster
> > >
> > > 'uname -a' output:
> > >  Linux ndn1 4.19.66+ #1253 Thu Aug 15 11:37:30 BST 2019 armv6l GNU/Linux
> > >
> > > I’ve use the default settings in both ‘client.conf’ and ‘nfd.conf’ within the ‘/usr/local/etc/ndn/' folder.
> > >
> > > My question is, when I followed the installation guide and installed NFD (http://named-data.net/doc/NFD/current/INSTALL.html) on my Ubuntu desktop & server
> > > 18.04.3 LTS and macOS High Sierra & macOS Mojave, everything was working fine. I was able to test ndnping etc. But on my Raspbian Buster, I got the following error (partial error output below):
> > >
> > > ——————————
> > > 1566699843.832553 FATAL: [nfd.Main] ../ndn-cxx/security/v2/key-chain.cpp(659): Throw in function prepareSignatureInfo
> > > Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<ndn::security::v2::KeyChain::InvalidSigningInfoError> >
> > > std::exception::what: Signing identity `/localhost/operator` does not have a default certificate
> > > ——————————
> > >
> > > I’ve tried configuring the NDN certificate by doing the following:
> > >  sudo mkdir -p /usr/local/etc/ndn/keys/
> > >  ndnsec-cert-dump -i /`whoami` > default.ndncert
> > >  sudo mv default.ndncert /usr/local/etc/ndn/keys/default.ndncert
> > >
> > > and adding the following configuration to my ‘nfd.conf’:
> > > ———
> > >  certfile keys/default.ndncert
> > >
> > >  privileges ; set of privileges granted to this identity
> > >   {
> > >    faces
> > >    fib
> > >    cs
> > >    strategy-choice
> > >  }
> > > ———
> > >
> > > but the problem still persist. My question is, is there any other configuration required as such problem did not occur in my Ubuntu and macOS installations.
> > >
> > > Best regards
> > > Adil - Malaysia
> > >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20190825/7ad548f7/attachment-0001.html>