Dmitry

If it helps, I used WSL2 for debugging on Linux under Win (https://docs.microsoft.com/en-us/visualstudio/test/remote-testing?view=vs-2022#:~:text=Remote%20testing%20enables%20developers%20to,Windows%20or%20Linux%20operating%20systems.) The pure Linux runner fails the tests as well.

I'm relatively new to this topic, but what is the actual impact of failed ValidateTrustChainSubAnchor on Linux? My understanding is it's required for attestation. But all input data is provided...

Any progress by any chance? :)

Sounds good to me but with a couple of suggestions / observations: 1. Most likely you will need a custom dual license. AGPL is not nuget friendly 😊 2. Review...

Hm, this can be related - https://github.com/actions/setup-dotnet/issues/323 Try to use include-prerelease and/or use @v3 vs current @v1 and see if it changes anything.

+ I would probably drop 3.1 (very close to EOL) and 5.0 (EOL) support, but I'm not the owner :)

@solrevdev I think we have some hardcoded stuff in the workflow: https://github.com/security-code-scan/security-code-scan/blob/vs2019/.github/workflows/pr.yml#L11 Meaning, this PR is still using @v1. You can check `Setup .NET SDK` step and observe `Run actions/setup-dotnet@v1`....

Oh, and include-prerelease doesn't exist in @v3. I also updated MS Build action to @1.1.3 in my experiments: - name: Setup .NET SDK uses: actions/setup-dotnet@v3 with: dotnet-version: | 3.1.x 5.0.x...

> `.github/workflows/build.yml` are not being run via the github actions/workflows and wont be until that file is committed to main/master? Yes, PR build will use the origin, instead of your...

Folks (@solrevdev @mac2000 @rallsmanEmpowerTech @StormPooper etc.) , I created a stand-alone fork of SecurityCodeScan. Can be easier to support in the future. If you are interested, please take a look....