Creating OpenSSL binaries with Control flow guard enabled fails with multiple test failure

Open
#22,554 17 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
c

Research direction

Start by reproducing the reported Windows build with perl Configure VC-WIN64A enable-fips enable-capieng --prefix=D:\opensslBuild\x64\dll --openssldir=D:\opensslBuild\openssldir no-shared and the /guard:cf flags. Identify which tests fail with those flags, compare them with the successful build without the flags, and consider the issue done when the non-shared FIPS build passes its tests with control flow guard enabled.

Written by the indexing model from the issue text.

Description

branch: master help wanted triaged: feature

I am trying to create a non-shared fips enabled build with control flow guard enabled:

command used:
perl Configure VC-WIN64A enable-fips enable-capieng --prefix=D:\opensslBuild\x64\dll --openssldir=D:\opensslBuild\openssldir no-shared CFLAGS=/guard:cf LDFLAGS=/guard:cf LIB_CFLAGS=/guard:cf

This is failing with multiple test failures.

Without using CFLAGS=/guard:cf LDFLAGS=/guard:cf LIB_CFLAGS=/guard:cf , Build is successfuly created.

Dominant language
C
Stars
30.8k
Forks
11.5k
Avg merge
10m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openssl/openssl

All issues in openssl/openssl

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.