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

add initial 1.4 wip #2957

Open
wants to merge 43 commits into
base: 1.4WIP
Choose a base branch
from
Open

add initial 1.4 wip #2957

wants to merge 43 commits into from

Conversation

jyao1
Copy link
Member

@jyao1 jyao1 commented Jan 15, 2025

No description provided.

Signed-off-by: Jiewen Yao <[email protected]>
jyao1 added 27 commits January 15, 2025 12:41
Signed-off-by: Jiewen Yao <[email protected]>
Signed-off-by: Jiewen Yao <[email protected]>
Signed-off-by: Jiewen Yao <[email protected]>
@jyao1 jyao1 force-pushed the 1.4WIP branch 4 times, most recently from dcf674e to c0a8bc7 Compare January 15, 2025 05:14
Copy link
Contributor

@steven-bellock steven-bellock left a comment

Choose a reason for hiding this comment

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

Need to go over how this should be split up into smaller commits and pull requests.

@@ -0,0 +1,31 @@
/**
* Copyright Notice:
* Copyright 2021-2024 DMTF. All rights reserved.
Copy link
Contributor

Choose a reason for hiding this comment

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

All new files need Copyright 2025 DMTF.

Copy link
Member Author

@jyao1 jyao1 Jan 16, 2025

Choose a reason for hiding this comment

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

One question: When do you think we will merge into main?

I prefer to change that when we merge to main.

It is meaningless to change it to 2025 now, and change again if we merge in 2026.

@@ -939,6 +939,10 @@ else()
add_subdirectory(os_stub/spdm_device_secret_lib_null)
add_subdirectory(os_stub/spdm_cert_verify_callback_sample)

add_subdirectory(os_stub/oqslib)
add_subdirectory(os_stub/pqccryptlib_oqs)
Copy link
Contributor

Choose a reason for hiding this comment

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

pqccryptlib_oqs -> cryptlib_liboqs

Copy link
Member Author

Choose a reason for hiding this comment

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

I think we need to add pqc prefix - pqccryptlib_liboqs, because it is not parallel to cryptlib_openssl or cryptlib_mbedtls.

README.md Outdated
@@ -171,6 +174,8 @@ For other architectures, refer to [build](https://github.com/DMTF/libspdm/blob/m

2) [OpenSSL](https://www.openssl.org) as cryptography library. Version 3.0.14.

3) [OQS](https://github.com/open-quantum-safe/liboqs) as PQC cryptography library. Version 0.12.0.
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this intended to be a long-lived cryptography library, or just one that will be used for development and eventually MbedTLS and OpenSSL will support PQC in production?

Copy link
Member Author

@jyao1 jyao1 Jan 16, 2025

Choose a reason for hiding this comment

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

I would say: If MbedTLS and OpenSSL support PQC in production, we can remove OQS for sure.

But before that, we have to use OQS for development. And I don't know WHEN the mbedTLS or OpenSSL will be ready.

If there is worry about quality, we can clarify, something like: "please read the OQS release note, to understand the production level."

Copy link
Member Author

Choose a reason for hiding this comment

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

I added clarification.

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