Actions
User Story #302
open
Epic #49: Implement user, groups and permissions management
Feature #273: Module identity
As an operator, I want the platform to be sure which module it is talking to, so that nothing else on the machine can pretend to be one
User Story #302:
As an operator, I want the platform to be sure which module it is talking to, so that nothing else on the machine can pretend to be one
Start date:
Due date:
% Done:
0%
Estimated time:
Description
A module extends the platform itself and may declare permissions, so an impostor would be serious. Its identity comes from being installed, with nothing for anyone to copy or store.
Acceptance criteria
- A module is identified without an operator having to handle a secret
- The platform and the module agree on protocol version before anything else happens
- The channel between them is protected and mutually verified
- A process that fails the exchange is refused and the attempt is recorded
- Installed modules are listed with their version and state
Rejection reason
Superseded by the rewritten epic #49
Updated by
Actions