Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Create SECURITY.md #257

Merged
merged 2 commits into from
Sep 21, 2023
Merged

Create SECURITY.md #257

merged 2 commits into from
Sep 21, 2023

Conversation

baentsch
Copy link
Member

Copy link
Member

@SWilson4 SWilson4 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine to me. Although it seems like we don't have any obvious disclaimer in documentation for oqs-provider like we do for liboqs. (Obvious as in I didn't spot it while scanning the README and USAGE files.) This might be a good place to include one---if that's something we want.

@baentsch
Copy link
Member Author

we don't have any obvious disclaimer in documentation for oqs-provider

Added with latest commit. Feedback solicited as to whether there's more component disclaimers we'd like/should list.

@baentsch baentsch merged commit 6d1ce18 into main Sep 21, 2023
@baentsch baentsch deleted the baentsch-patch-1 branch September 21, 2023 07:40
feventura pushed a commit to EntrustCorporation/oqs-provider that referenced this pull request Mar 16, 2024
* Create SECURITY.md

* disclaimers added to documentation [skip ci]

Signed-off-by: Felipe Ventura <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants