S02-RA: Yes
Rationale
In the selected SSH2-inspired enrollment mode, an IPCP uses a locally generated RSA key pair. Peers install its public key under its application-process name and decide locally whether to accept that binding. No certificate authority or external identity issuer is required.
Assessment method
Pinned documentation and authentication source inspection with explicit policy selection; no execution or audit
Source context
IRATI SSH2-inspired authentication policy
Outstanding qualification
Scoped to IPCP cryptographic identity, not civil identity, automatic trust or arbitrary application identity. The README describes local key generation; load_authentication_keys reads local private and pinned peer-public keys. Administrative provisioning remains necessary and is not credited as unprivileged operation.
Public sources
- https://github.com/IRATI/stack/blob/726b535c908f8a74e8c68dd493cfbb1bd8726546/librina/src/security-manager.cc
- https://github.com/IRATI/stack/blob/726b535c908f8a74e8c68dd493cfbb1bd8726546/README.md
- https://github.com/IRATI/stack/blob/726b535c908f8a74e8c68dd493cfbb1bd8726546/rinad/src/ipcp/plugins/sm-auth-psoc/sm-auth-psoc-plugin.cc
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round665.html