Skip to content

Enforce HTTPS: add SLES/openSUSE certificate trust instructions (#28292) - #37675

Open
baylavdev wants to merge 1 commit into
dotnet:mainfrom
baylavdev:docs/enforcing-ssl-sles
Open

baylavdev wants to merge 1 commit into
dotnet:mainfrom
baylavdev:docs/enforcing-ssl-sles

Conversation

@baylavdev

@baylavdev baylavdev commented Sep 17, 2026

Copy link
Copy Markdown

What

Replaces the "see issue #28292" placeholder and the commented-out RHEL copy in aspnetcore/security/enforcing-ssl.md with a real Trust the certificate on SUSE Linux Enterprise Server (SLES) and openSUSE section:

  • dependency install with the SUSE package name (mozilla-nss-tools provides certutil)
  • export the development certificate
  • trust in Chromium-based browsers and in Firefox (certutil)
  • trust in curl/OpenSSL clients (--cacert, or SSL_CERT_DIR via the existing OpenSSL trust section)
  • cleanup
  • a note explaining why adding the certificate to /etc/pki/trust/anchors/ + update-ca-certificates does not work (the dev cert is CA:FALSE; p11-kit lists it as an anchor but omits it from the bundles, so OpenSSL keeps rejecting it)

Fixes #28292. Contributes to #27603 (SLES coverage; the RHEL/tabs restructuring in that issue is out of scope here).

Why

The page has pointed SLES users at a GitHub issue since 2023, and the commented-out block was a straight copy of the RHEL steps with dnf, which doesn't apply. Two earlier volunteers dropped the item for lack of a SLES environment to verify on.

How

  • Every command was run on registry.suse.com/bci/dotnet-sdk:8.0 (SLES 15 SP7) and registry.opensuse.org/opensuse/leap:15.6, including the negative result for the system trust store.
  • Heading promoted from #### (nested under the linux-dev-certs subsection by accident) to ###, a sibling of the other Linux subsections.
  • Kept the placeholder-variable style used elsewhere in the article (${CertificateDirectory}, ${UserProfile}) and the [!WARNING]/[!NOTE] alert syntax.
  • ms.date updated.

Checklist

  • Steps verified on SLES 15 SP7 and openSUSE Leap 15.6
  • Links resolve (#openssl-trust is an existing heading in the article)
  • No changes outside the SLES section and ms.date
  • Follows existing article conventions (alerts, placeholders, heading levels)

Internal previews

File Preview link
aspnetcore/security/enforcing-ssl.md Learn preview

Build report

Replaces the SLES placeholder (and the commented-out RHEL copy) with steps
verified on SLES 15 SP7 and openSUSE Leap 15.6: zypper package names,
certutil for Chromium/Firefox, curl --cacert, cleanup, and a note on why
the system trust store does not accept the CA:FALSE dev certificate.

Fixes dotnet#28292
Contributes to dotnet#27603
@baylavdev

Copy link
Copy Markdown
Author

@dotnet-policy-service agree

@baylavdev baylavdev changed the title Enforce HTTPS: add SLES/openSUEnforce HTTPS: add SLES/openSUSE certificate trust instructions (#28292)SE certificate trust instructions Enforce HTTPS: add SLES/openSUSE certificate trust instructions (#28292) Sep 17, 2026
@guardrex
guardrex requested a review from tdykstra September 17, 2026 14:16
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.

Trust HTTPS certificate on SLES

2 participants