Jump to content
Toggle sidebar
Logos
Search
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Tools
What links here
Related changes
Special pages
Page information
Editing
Modman/Requirements
(section)
Page
Discussion
English
Read
Edit
View history
More
Read
Edit
View history
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==== 4.6.2 Functional Requirements ==== MSF-001: Trust Management System - The system MUST implement trust management: * Allow trust delegation for specific packages or package patterns only * Support hierarchical trust relationships * Enable fine-grained trust revocation * Prevent trust escalation attacks * SHOULD support negative trust assertions (package blacklisting) MSF-002: Package Verification System - The system MUST verify packages: * Verify package signatures before installation * Validate package metadata independently of packages * Check package metadata matches signed metadata * Prevent package metadata tampering * Support multiple package formats * Enable secure dependency resolution MSF-003: Authentication System - The system MUST authenticate entities: * Verify module signatures * Validate developer identities * Check certificate chains * Support decentralized certification MSF-004: Supply Chain Security - The system MUST secure supply chain: * Track module provenance * SHOULD verify build reproducibility * MUST detect tampering * SHOULD implement reputation-based trust * SHOULD support peer reputation scoring MSF-005: Network Security Protocol - The system MUST secure communications: * Encrypt communications * Prevent MitM attacks * Handle malicious peers * Support peer blacklisting * Implement trust revocation MSF-006: Device Security System - The system MUST secure devices: * Handle heterogeneous device capabilities * Protect resource-constrained devices * Support secure offline operation * Implement secure peer discovery <span id="other-nonfunctional-requirements"></span>
Summary:
Please note that all contributions to Logos may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Logos:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)