You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Correct eSec implementation status and scope documentation #2
The repository documentation does not accurately distinguish the security functionality already implemented in eos from the portion that remains incomplete. Correct the status and point readers to the actual implementation.
Duplicate of #1 (same author, same ask — correct the status/scope docs). The current README now distinguishes implemented crypto (AES/SHA-256/SHA-512, NIST vectors) from stubs (RSA/ECC behind EOS_ALLOW_STUB_CRYPTO) and points at eos/services/{security,crypto} plus ADR-012. Closing as duplicate; #1 stays open as the tracker. See also #5 (merge proposal).
Activity
Aswin-V commentedon Oct 1, 2026
Duplicate of #1 (same author, same ask — correct the status/scope docs). The current README now distinguishes implemented crypto (AES/SHA-256/SHA-512, NIST vectors) from stubs (RSA/ECC behind EOS_ALLOW_STUB_CRYPTO) and points at eos/services/{security,crypto} plus ADR-012. Closing as duplicate; #1 stays open as the tracker. See also #5 (merge proposal).