Actions
Bug #2009
closed
SecPublicInfoSqlite3 is unsafe on NFS share
Start date:
09/25/2014
Due date:
% Done:
100%
Estimated time:
0.50 h
Description
Environment: multiple machines with $HOME pointing to same NFS share; $HOME/.ndn does not exist
Steps to reproduce:
- at all machines, simultaneously run an app that uses KeyChain
Actual: "key does not exist" error
Expected: no error
Updated by Junxiao Shi about 10 years ago
- Has duplicate Bug #1790: NLSR throws exception and quits if executed simultaneously on all machines in emulab environment. added
Updated by Junxiao Shi about 10 years ago
According to #1790 note-2, it's recommended not to share $HOME/.ndn across machines.
One acceptable solution to this bug is to document this recommendation, without changing code.
Updated by Alex Afanasyev about 10 years ago
There is nothing to change in the code now. Private keys should not be shared between machines, NFS or not NFS.
There is an option to the library --without-sqlite-locking which helps in some cases, but doubt it will work in this particular case.
Updated by Junxiao Shi about 10 years ago
From note-2:
One acceptable solution to this bug is to document this recommendation, without changing code.
Updated by Junxiao Shi about 8 years ago
- Status changed from New to Code review
- Assignee set to Junxiao Shi
- Target version set to v0.5
- % Done changed from 0 to 100
- Estimated time set to 0.50 h
Updated by Junxiao Shi about 8 years ago
- Status changed from Code review to Closed
Actions