Skip to content

Refactor ct::eq_bytes to use an unsafe read_votatile #128

Open
Open
Refactor ct::eq_bytes to use an unsafe read_votatile#128
Assignees
ounsworth

Description

@ounsworth
ounsworth
opened on Sep 10, 2026

The current constant-time equality uses BlackBox, which is not a great solution.

the bouncycastle-utils crate is allowed to use Unsafe Rust. A better solution would be to do something with read_volatile and write_volatile.

Activity

  1. ounsworth
    self-assigned this
    on Sep 12, 2026
  2. dghgit
    added a commit that references this issue on Sep 30, 2026

    Merge PR #131 (utils ct: volatile optimisation barrier for Condition …

    3d01899
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