Skip to content

Initialize certificate: default to SHA-1 when necessary#10173

Open
SparkiDev wants to merge 1 commit intowolfSSL:masterfrom
SparkiDev:init_cert_sha1
Open

Initialize certificate: default to SHA-1 when necessary#10173
SparkiDev wants to merge 1 commit intowolfSSL:masterfrom
SparkiDev:init_cert_sha1

Conversation

@SparkiDev
Copy link
Copy Markdown
Contributor

Description

Make SHA-1 with RSA signature type the last option.
SHA-1 signatures are deprecated as weak.

Fixes #10078

Testing

Standard builds

@DrKatieL
Copy link
Copy Markdown

DrKatieL commented Apr 9, 2026

The PR fixes the issue. Thank you!

@SparkiDev SparkiDev assigned wolfSSL-Bot and unassigned SparkiDev Apr 9, 2026
@SparkiDev SparkiDev requested a review from wolfSSL-Bot April 9, 2026 05:11
dgarske

This comment was marked as duplicate.

Copy link
Copy Markdown
Contributor

@dgarske dgarske left a comment

Choose a reason for hiding this comment

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

🐺 Skoll Code Review

Overall recommendation: REQUEST_CHANGES
Findings: 2 total — 2 posted, 0 skipped

Posted findings

  • [Critical] Inverted preprocessor condition: defined(NO_SHA) should be !defined(NO_SHA)wolfcrypt/src/asn.c:24996
  • [Medium] Test fallback to SHAwRSA/SHAwECDSA does not guard against NO_SHAwolfcrypt/test/test.c:24514-24515

Review generated by Skoll via openclaw

Make SHA-1 with RSA signature type the last option.
SHA-1 signatures are deprecated as weak.
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.

[Bug]: wc_InitCert_ex uses a deprecated default algorithm (SHA1)

4 participants