Skip to content

Clarify formal security claims #129

Description

@nadimkobeissi

This repository claims the following, in README.md:

An IoT friendly, formally verified, crypto library based on libcrux.

Humans on the Earth are interested in assessing the security of this library. But in order to do so, and to avoid protracted debates in the event of any findings, the library must first expand on what it means by "formally verified" by providing clear security claims of targeted security guarantees.

Do you, for example, claim to provide timing attack resistance and secret independence, or only functional correctness?

Elaboration on these topics in the form of clear, precise claims would be welcome.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions