Consider FIPS testing

Open
#110,625 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, linux
Domain
infrastructure, security, testing-qa

Research direction

Start by reviewing dotnet-docker issues 5849 and 6104, then inspect dotnet/runtime PR 108967 to understand the planned Azure Linux VM testing. Done would require a decided plan for FIPS-enabled VM coverage, validation of relevant scenarios, and documented forbidden APIs in collaboration with the Azure Linux team.

Written by the indexing model from the issue text.

Description

area-System.Security

We have two recent issues that relate to FIPS:

It is expected that a growing set of users will be running .NET containers on FIPS enabled hosts. I expect that FIPS testing will help us better understand and validate the scenarios that do and do not work in that environment. It would also be useful for us to publish which APIs are forbidden in FIPS mode, which may change with distro version. We would do that in collaboration with the Azure Linux team.

We already have a plan to switch testing to Azure Linux VMs:

That change would not have found these issues. We should consider a second Azure Linux VM variant that is FIPS enabled for more targeted FIPS-related testing.

Dominant language
C#
Stars
18.3k
Forks
5.6k
PR metrics pending

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 dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.