Skip to content

Set OpenSSL SHA1 flag in build scripts - #3849

Merged
siegfriedpammer merged 1 commit into
masterfrom
set-openssl-sha1-in-build-scripts
Jul 2, 2026
Merged

Set OpenSSL SHA1 flag in build scripts#3849
siegfriedpammer merged 1 commit into
masterfrom
set-openssl-sha1-in-build-scripts

Conversation

@siegfriedpammer

@siegfriedpammer siegfriedpammer commented Jul 2, 2026

Copy link
Copy Markdown
Member

Summary

  • Set OPENSSL_ENABLE_SHA1_SIGNATURES=1 directly in restore, build, update-deps, clean, publish, local publish, and format scripts before they invoke dotnet or the formatter hook.
  • Export the same variable in the pre-commit formatter hook for direct hook usage.

Verification

  • env -u OPENSSL_ENABLE_SHA1_SIGNATURES pwsh ./build.ps1 -Configuration Debug --no-restore
  • env -u OPENSSL_ENABLE_SHA1_SIGNATURES pwsh ./BuildTools/format.ps1
  • git diff --check origin/master...HEAD

Local OpenSSL defaults can reject legacy SHA-1 signatures during dotnet operations. Set the required compatibility flag inside the repository scripts so restore, build, publish, clean, and formatting paths do not depend on each caller's shell environment.

Assisted-by: OpenCode:openai/gpt-5.5:OpenCode
@siegfriedpammer
siegfriedpammer force-pushed the set-openssl-sha1-in-build-scripts branch from d495680 to 2849cb5 Compare July 2, 2026 11:34
@siegfriedpammer
siegfriedpammer merged commit 6b2852c into master Jul 2, 2026
13 checks passed
@siegfriedpammer
siegfriedpammer deleted the set-openssl-sha1-in-build-scripts branch July 7, 2026 13:50
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.

1 participant