crypto/x509: defer directory scan when cert bundle provides roots by trivenay · Pull Request #80374 · golang/go

trivenay · 2026-07-11T09:01:37Z

On systems where a cert bundle file (e.g. ca-certificates.crt) is
available and contains root certificates, skip eagerly scanning the
default cert directories. On most systems the bundle is a concatenation
of the individual certificates in the directory, so scanning reads the
same certificates again redundantly.

The deferred directories are stored on the CertPool and loaded on
demand if chain construction using the bundle roots fails. This ensures
backward compatibility for setups where a directory contains
certificates not present in the bundle.

When SSL_CERT_DIR is explicitly set by the user, directories are always
scanned eagerly, as the user may be intentionally combining certificates
from multiple sources.

On Fedora, RHEL, and Amazon Linux 2023 systems, /etc/ssl/certs/
contains 430-750 entries. After the existing same-directory symlink
filter, 150-253 individual files remain. Reading and parsing these on a
CPU-constrained environment (e.g. 128MB container with 0.08 vCPU) costs
~820ms and produces zero new certificates beyond what the bundle already
provides.

On standard Fedora/RHEL systems with full CPU:
Cert loading time reduced from ~12ms to ~3ms

On CPU-constrained systems (e.g. 128MB container with 0.08 vCPU):
Amazon Linux 2023: ~1510ms before, ~398ms after

Updates #38869
Updates #74613

gopherbot · 2026-07-11T09:14:39Z

This PR (HEAD: f0a370b) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/799801.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2026-07-11T09:30:39Z

Message from Gopher Robot:

Patch Set 1:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2026-07-11T09:30:40Z

Message from Gopher Robot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
A maintainer will review your change and provide feedback. See
https://go.dev/doc/contribute#review for more info and tips to get your
patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11 or adds a tag like "wait-release", it means that this CL will be
reviewed as part of the next development cycle. See https://go.dev/s/release
for more details.

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2026-07-11T11:39:45Z

Message from Naman Trivedi:

Patch Set 4:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2026-07-13T06:38:56Z

This PR (HEAD: 0d07e45) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/799801.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2026-07-13T07:47:58Z

This PR (HEAD: da3a3d8) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/799801.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

21region · 2026-07-15T17:11:54Z

+			for _, fi := range fis {
+				data, err := os.ReadFile(directory + "/" + fi.Name())
+				if err == nil {
+					s.AppendCertsFromPEM(data)


This mutates byName, haveSum, and lazyCerts while other goroutines may concurrently read them in findPotentialParents. sync.Once only serializes directory loading; it does not protect those readers, so concurrent certificate verification can race here.

gopherbot · 2026-07-15T19:25:14Z

This PR (HEAD: 1942513) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/799801.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2026-07-16T08:03:03Z

This PR (HEAD: 881b86d) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/799801.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2026-07-16T08:58:11Z

This PR (HEAD: eaf3483) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/799801.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2026-07-16T09:16:35Z

This PR (HEAD: d79b794) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/799801.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2026-07-16T09:52:42Z

This PR (HEAD: 2fedffa) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/799801.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2026-07-16T11:06:26Z

This PR (HEAD: 2d61d29) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/799801.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2026-07-16T11:24:03Z

This PR (HEAD: fb07c68) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/799801.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2026-07-16T13:11:53Z

This PR (HEAD: c0a16aa) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/799801.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2026-08-03T10:16:14Z

Message from Naman Trivedi:

Patch Set 15:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2026-08-03T20:10:05Z

Message from Emmanuel Odeke:

Patch Set 15: Commit-Queue+1

(4 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2026-08-03T20:10:06Z

Message from golang-scoped@luci-project-accounts.iam.gserviceaccount.com:

Patch Set 15:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2026-08-03T19:50:50Z","revision":"e3328fd7164d59dea0570f5d2b3b3d24bd781524"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2026-08-03T20:28:00Z

Message from Emmanuel Odeke:

Patch Set 15: -Commit-Queue

(Performed by <GERRIT_ACCOUNT_60063> on behalf of <GERRIT_ACCOUNT_5137>)

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2026-08-03T20:28:00Z

Message from golang-scoped@luci-project-accounts.iam.gserviceaccount.com:

Patch Set 15:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2026-08-03T20:28:01Z

Message from golang-scoped@luci-project-accounts.iam.gserviceaccount.com:

Patch Set 15: LUCI-TryBot-Result+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2026-08-03T22:18:58Z

This PR (HEAD: 86e7c64) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/799801.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2026-08-03T22:37:03Z

Message from Naman Trivedi:

Patch Set 15:

(5 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2026-08-03T22:37:04Z

Message from Emmanuel Odeke:

Patch Set 16: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2026-08-03T22:54:52Z

Message from golang-scoped@luci-project-accounts.iam.gserviceaccount.com:

Patch Set 16:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2026-08-03T22:25:03Z","revision":"88445aeb0b7e1c951eb551f3040249afe492effb"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2026-08-03T22:54:52Z

Message from Emmanuel Odeke:

Patch Set 16: -Commit-Queue

(Performed by <GERRIT_ACCOUNT_60063> on behalf of <GERRIT_ACCOUNT_5137>)

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2026-08-03T22:54:53Z

Message from golang-scoped@luci-project-accounts.iam.gserviceaccount.com:

Patch Set 16:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2026-08-03T22:54:53Z

Message from golang-scoped@luci-project-accounts.iam.gserviceaccount.com:

Patch Set 16: LUCI-TryBot-Result+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2026-08-06T15:16:46Z

Message from Naman Trivedi:

Patch Set 16:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2026-08-13T17:12:52Z

Message from Daniel McCarney:

Patch Set 16:

(6 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2026-08-13T20:01:23Z

Message from Naman Trivedi:

Patch Set 16:

(5 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2026-08-13T20:57:40Z

This PR (HEAD: 4912a90) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/799801.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

On systems where a cert bundle file (e.g. /etc/ssl/certs/ca-certificates.crt) is available and contains root certificates, skip eagerly scanning the default cert directories. On most systems the bundle is a concatenation of the individual certificates in the directory, so scanning reads the same certificates again redundantly. The deferred directories are stored on the CertPool and loaded on demand if a certificate lookup misses during verification. This ensures backward compatibility for setups where a directory contains certificates not present in the bundle. When SSL_CERT_DIR is explicitly set by the user, directories are always scanned eagerly, as the user may be intentionally combining certificates from multiple sources. On Fedora, RHEL, and Amazon Linux 2023 systems, /etc/ssl/certs/ contains ~430-750 entries. After the existing same-directory symlink filter, ~150-253 individual files remain. Reading and parsing these on a CPU-constrained environment (e.g. 128MB AWS Lambda with 0.08 vCPU) costs ~820ms and produces zero new certificates beyond what the bundle already provides. Benchmark on AWS Lambda (128MB, provided.al2023): Before: first TLS call takes ~1510ms After: first TLS call takes ~398ms (74% reduction) The optimization also benefits standard Fedora/RHEL systems: Fedora 39: directory scan reduced from ~11ms to 0ms Amazon Linux 2023: directory scan reduced from ~9ms to 0ms Fixes golang#38869 Updates golang#74613

gopherbot · 2026-08-13T21:15:21Z

This PR (HEAD: 2ef4e90) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/799801.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2026-08-13T21:34:34Z

Message from Naman Trivedi:

Patch Set 16:

(5 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/799801.
After addressing review feedback, remember to publish your drafts!

This was referenced Jul 11, 2026

crypto/x509: stop looking at first root store #38869

Open

crypto/tls: slow(er) creation of TLS/SSL clients under certain environments #74613

Closed

trivenay mentioned this pull request Jul 11, 2026

proposal: crypto/x509: tighten SSL_CERT_FILE / SSL_CERT_DIR behavior #79496

Open

trivenay force-pushed the x509-dedup-inode branch from f0a370b to 0d07e45 Compare July 13, 2026 06:35

trivenay force-pushed the x509-dedup-inode branch from 0d07e45 to da3a3d8 Compare July 13, 2026 07:39

21region reviewed Jul 15, 2026

View reviewed changes

trivenay force-pushed the x509-dedup-inode branch 2 times, most recently from 1e6e3f4 to 1942513 Compare July 15, 2026 19:18

trivenay force-pushed the x509-dedup-inode branch 2 times, most recently from ecdf513 to 881b86d Compare July 16, 2026 07:50

trivenay force-pushed the x509-dedup-inode branch from 881b86d to eaf3483 Compare July 16, 2026 08:50

trivenay force-pushed the x509-dedup-inode branch 2 times, most recently from 6aebe89 to d79b794 Compare July 16, 2026 09:12

trivenay force-pushed the x509-dedup-inode branch from d79b794 to 2fedffa Compare July 16, 2026 09:36

trivenay force-pushed the x509-dedup-inode branch from 2fedffa to 2d61d29 Compare July 16, 2026 11:04

trivenay force-pushed the x509-dedup-inode branch from 2d61d29 to fb07c68 Compare July 16, 2026 11:13

trivenay force-pushed the x509-dedup-inode branch from fb07c68 to c0a16aa Compare July 16, 2026 13:08

trivenay force-pushed the x509-dedup-inode branch from c0a16aa to 86e7c64 Compare August 3, 2026 22:02

trivenay force-pushed the x509-dedup-inode branch from 86e7c64 to 4912a90 Compare August 13, 2026 20:52

trivenay force-pushed the x509-dedup-inode branch from 4912a90 to 2ef4e90 Compare August 13, 2026 20:58

Uh oh!

Conversation

trivenay commented Jul 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gopherbot commented Jul 11, 2026

Uh oh!

gopherbot commented Jul 11, 2026

Uh oh!

gopherbot commented Jul 11, 2026

Uh oh!

gopherbot commented Jul 11, 2026

Uh oh!

gopherbot commented Jul 13, 2026

Uh oh!

gopherbot commented Jul 13, 2026

Uh oh!

21region Jul 15, 2026

Choose a reason for hiding this comment

Uh oh!

gopherbot commented Jul 15, 2026

Uh oh!

gopherbot commented Jul 16, 2026

Uh oh!

gopherbot commented Jul 16, 2026

Uh oh!

gopherbot commented Jul 16, 2026

Uh oh!

gopherbot commented Jul 16, 2026

Uh oh!

gopherbot commented Jul 16, 2026

Uh oh!

gopherbot commented Jul 16, 2026

Uh oh!

gopherbot commented Jul 16, 2026

Uh oh!

gopherbot commented Aug 3, 2026

Uh oh!

gopherbot commented Aug 3, 2026

Uh oh!

gopherbot commented Aug 3, 2026

Uh oh!

gopherbot commented Aug 3, 2026

Uh oh!

gopherbot commented Aug 3, 2026

Uh oh!

gopherbot commented Aug 3, 2026

Uh oh!

gopherbot commented Aug 3, 2026

Uh oh!

gopherbot commented Aug 3, 2026

Uh oh!

gopherbot commented Aug 3, 2026

Uh oh!

gopherbot commented Aug 3, 2026

Uh oh!

gopherbot commented Aug 3, 2026

Uh oh!

gopherbot commented Aug 3, 2026

Uh oh!

gopherbot commented Aug 3, 2026

Uh oh!

gopherbot commented Aug 6, 2026

Uh oh!

gopherbot commented Aug 13, 2026

Uh oh!

gopherbot commented Aug 13, 2026

Uh oh!

gopherbot commented Aug 13, 2026

Uh oh!

gopherbot commented Aug 13, 2026

Uh oh!

gopherbot commented Aug 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

trivenay commented Jul 11, 2026 •

edited

Loading