Skip to content

Correct eSec implementation status and scope documentation #2

Closed as duplicate

Description

@srpatcha

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.

Activity

  1. Aswin-V commented on Oct 1, 2026

    @Aswin-V
    Contributor

    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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions