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

apps/mbedtls: add compilation configuration #2744

Merged
merged 1 commit into from
Oct 17, 2024

Conversation

ThePassionate
Copy link

Summary

1.Supplement cmake to compile POLY1305/RIPEMD160/Bignum algorithms
2.Add blowfish and arc4 algorithm configuration

Impact

compile

Testing

ci

1.Supplement cmake to compile POLY1305/RIPEMD160/Bignum algorithms
2.Add blowfish and arc4 algorithm configuration

Signed-off-by: makejian <[email protected]>
@nuttxpr
Copy link

nuttxpr commented Oct 16, 2024

[Experimental Bot, please feedback here]

This PR does not meet the NuttX requirements.

Here's why and how to improve it:

  • Summary:
    • Missing Information:
      • Why? The summary lacks a clear explanation of why these changes are necessary. Are you fixing a bug, adding new features, or optimizing existing ones?
      • Functionality: Be specific about which parts of the code are affected. For example, mention the specific files or modules where the changes are implemented.
      • How? Briefly describe how the changes work. Do you introduce new functions, modify existing ones, or change the control flow?
      • Links: Provide links to any related NuttX or NuttX Apps issues or pull requests.
  • Impact:
    • Insufficient Detail: While you mention "compile" under impact, you need to elaborate on all the points mentioned in the requirements:
      • New Feature? Clearly state if this adds new cryptographic algorithms (POLY1305, RIPEMD160, Blowfish, ARC4).
      • User Impact? Will users need to change their code or configuration to use these algorithms?
      • Build Impact? How do these changes affect the build process? Are there new configuration options? New dependencies?
      • Hardware Impact? Do these algorithms have specific hardware requirements or optimizations for certain architectures?
      • Documentation? Will the documentation need updating to reflect these new algorithms? If so, have you made those updates in this PR?
      • Security? Carefully consider and describe any potential security implications. Are these well-established algorithms? Are there known vulnerabilities?
      • Compatibility? Do these changes affect compatibility with previous NuttX versions or other software that might rely on the cryptographic libraries?
  • Testing:
    • Incomplete:
      • Build Hosts: Provide details about your development environment:
        • Operating System (e.g., Ubuntu 20.04, macOS Monterey)
        • CPU architecture (e.g., x86_64, ARM64)
        • Compiler (e.g., GCC 11.2, Clang 13.0)
      • Targets: Specify the target architectures and boards you tested on:
        • Architecture (e.g., simulator sim, RISC-V, ARM Cortex-M4)
        • Board and Configuration (e.g., board-name:config-name)
      • Logs: "ci" is not sufficient. Include relevant snippets from your build logs and test output to demonstrate:
        • Successful compilation before and after your changes.
        • That the new algorithms function correctly (if possible, include test cases).

To improve your PR, provide comprehensive answers to each point in the requirements. This will help reviewers understand your changes and ensure a smoother review process.

@xiaoxiang781216 xiaoxiang781216 merged commit 6588ce4 into apache:master Oct 17, 2024
36 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants