Commit: c75605726e7281b68cc4dee4e895d3386ba7708f
Parent: 0cdcff2f90f0a2425527adafdb14cdf6cd033a99
Author: Brian Gix <brian.gix@intel.com>
Committer: Brian Gix <brian.gix@intel.com>
Date: 2019-10-01 20:42:02
Tree: 597b268960fc8bb81427d201840d011f868ba42b

mesh: Fix Key Ring permissions for local nodes We do *not* automatically create populated key rings for imported or joined nodes, but we also do not *forbid* any node from adding a key in it's possesion to the local key ring. There are two (known) use cases for Import() 1. Node previously existed on a different physical piece of hardware, and is being migrated to this daemon. 2. Node was newly provisioned Out-Of-Band, and this is the net result of the provisioning. In *neither* case is it a given that the Node should be able to provision another node (the effect of adding the Net Key to the key ring). In neither case is it a given that the Node should be able to modify it's own Config Server states (the effect of adding it's Device Key to the key ring).

Diffstat

M mesh/manager.c | 5 - - - - -
M mesh/node.c | 15 - - - - - - - - - - - - - - -

2 files changed, 0 insertions(+), 20 deletions(-)

View Full Diff | Patch