Bug #4274
closed
NFD quits if started with nfd-start without KeyChain
0%
Description
Environment: Ubuntu 14.04
Steps to reproduce:
- Use a non-root user with sudo privileges
- Install NFD from source code, and copy the sample nfd.conf
- Delete user's KeyChain:
sudo rm -rf $HOME/.ndn - Execute
nfd-start
Expected: NFD starts normally
Actual: NFD quits within a few seconds; there was no FATAL log
Updated by Junxiao Shi about 7 years ago
- Has duplicate Bug #4266: NFD won't start correctly on Vagrant integration testing environment added
Updated by Junxiao Shi about 7 years ago
- Description updated (diff)
- Assignee set to Zhiyi Zhang
- Estimated time set to 9.00 h
If user's KeyChain was chown'd to root (sudo chown -R root:root .ndn), NFD could start normally.
This means KeyChain v2 could not handle its files being owned by a non-root user while the calling process is executed as root.
The solution is to either modify KeyChain v2 to tolerate its files owned by another user, or update nfd-start and IntegrationTests to avoid starting NFD as root using user's KeyChain.
Updated by Davide Pesavento about 7 years ago
- Blocks deleted (Task #4275: Release 0.6.0)
Updated by Davide Pesavento almost 7 years ago
- Target version deleted (
v0.6) - Start date deleted (
09/07/2017)
Updated by Davide Pesavento about 1 year ago
- Category deleted (
Build) - Status changed from New to Rejected
- Assignee deleted (
Zhiyi Zhang)
I cannot reproduce, and I routinely follow the process outlined in "steps to reproduce" whenever I need to run a quick test with NFD. Never had a problem, at least not for the last several years.
We can reopen if we find another way to reproduce.