How can certs be added to the CurrentUser/My store on Linux?

Open Beginner friendly
#34,908 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
64/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
linux

Research direction

Start with docs/standard/security/cross-platform-cryptography.md and the CurrentUser/My discussion in the issue. Review the linked CertificateResolver.cs reference and determine what practical Linux certificate-store guidance or relevant instructions can be added. Done means the page explains how to populate the supported store so an application can discover the certificate.

Written by the indexing model from the issue text.

Description

:watch: Not Triaged dotnet/svc standard-library/subsvc

The page explains which scenarios are supported, but (at least to me) the explanation of how to actually populate the Linux stores with a certificate remains vague. It says "class is a projection of system trust decisions (read-only), user trust decisions (read-write), and user key storage (read-write)" and also "no user stores exist by default".

Is it possible to provide a bit more detail (e.g. link to relevant instructions) about how one would actually put a cert in the store so that an app can find it?

The CurrentUser/My store is of interest because that is what appears to be used under the hood by ProtectKeysWithCertificate (source). It checks the CurrentUser/My and LocalMachine/My; the latter is not supported on Linux according to the docs page.


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

Dominant language
No language data
Stars
4.8k
Forks
6.1k
Avg merge
15h 30m
Merged PRs (30d)
374

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/docs

All issues in dotnet/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.