Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Reliability #483

Open
4 tasks
baentsch opened this issue Aug 18, 2024 · 1 comment
Open
4 tasks

Reliability #483

baentsch opened this issue Aug 18, 2024 · 1 comment
Labels
help wanted Extra attention is needed

Comments

@baentsch
Copy link
Member

oqsprovider (and suitably limited liboqs configs) may be (are?) being used in settings considered "productive" despite a documented (standard) warning against this. Discussions as to how to reduce the risk of this have been started elsewhere (e.g., open-quantum-safe/tsc#1 and PQCA/TAC#44) but don't seem to garner much interest or concrete resolution proposals (or are even labelled only "enhancement").

Thus, this issue is to define a set of concrete features that this project should possess to be considered "reliable for everyday use" and sufficiently reducing the risks to its users deploying it -- and the risk to the code owners' reputation of having done the code.

Let me start by stating the obvious:

Further line items welcome (even if only adding already open issues).

@baentsch
Copy link
Member Author

baentsch commented Sep 6, 2024

Here's a nice "operational" test checklist of an OQS alternative that may be worth while following.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant