pub enum SecurityProfile {
Default,
AcceptSigned,
Disabled,
Custom(Arc<Validator>),
}Expand description
Configures how the engine validates Data packet signatures.
Security is default-on in NDN. Use Disabled only for benchmarking
or isolated lab environments.
Variants§
Default
Full chain validation with cert fetching and hierarchical trust.
This is the default. When a SecurityManager is set on the builder,
the engine wires a Validator with:
TrustSchema::hierarchical()(data and key share first component)- Shared
CertCachefrom theSecurityManager - Trust anchors from the
SecurityManager CertFetcherfor missing certificates
When no SecurityManager is set, the engine falls back to
AcceptSigned behaviour: each Data packet’s signature is verified
cryptographically but namespace hierarchy is not enforced. This keeps
security on by default even without a configured trust anchor.
Use Disabled to explicitly turn off all validation.
AcceptSigned
Verify that signatures are present and cryptographically valid, but skip trust schema and chain walking.
Useful for testing or deployments where any valid signature is sufficient (e.g., all participants share a trust domain).
Disabled
No validation — all Data packets pass through unchecked.
Must be explicitly set. Use only for benchmarking or isolated lab environments where security is irrelevant.
Custom(Arc<Validator>)
Custom validator provided by the caller.
Full control over trust schema, cert cache, trust anchors, and chain depth. For advanced use cases.