crypto/x509: "certificate is not standards compliant" on MacOS #51991

dims · 2022-03-28T19:12:49Z

We hit an error with a unit test we had in Kubernetes and started looking at the impact on end users of kubernetes if the problem is not resolved by the time kubernetes 1.24 is released. More context: please see Kubernetes issue - kubernetes/kubernetes#108956

What version of Go are you using (`go version`)?

$ go version
go version go1.18 darwin/arm64

Does this issue reproduce with the latest release?

Yes.

What operating system and processor architecture are you using (`go env`)?

go env Output

$ go env
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/Users/dims/Library/Caches/go-build"
GOENV="/Users/dims/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/dims/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/dims/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/opt/homebrew/Cellar/go/1.18/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/opt/homebrew/Cellar/go/1.18/libexec/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.18"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/qw/pkzvlrfs7rn7h6r1x7r57_rw0000gn/T/go-build1513460199=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

Please see https://go.dev/play/p/w4rr43vQv7d

What did you expect to see?

success

What did you see instead?

error: x509: “no-sct.badssl.com” certificate is not standards compliant

The text was updated successfully, but these errors were encountered:

dims · 2022-03-28T19:15:56Z

The error seems be introduced here: feb024f#diff-9e2a37df9605e8b207365b51999e6b14e1f5db72b27ad33514dbac502d477c25R212

@liggitt summarized the ask here : kubernetes/kubernetes#108956 (comment) and kubernetes/kubernetes#108956 (comment) on what impact this will have on kubernetes users for whom there was no issues before we switched to go1.17 when they try the kubernetes kubectl command built using go1.18.

Worst case we would like to document scenarios under which users will hit the certificate is not standards compliant error that they were not hitting before.

thanks!

seankhliao · 2022-03-28T20:49:13Z

cc @golang/security

FiloSottile · 2022-03-28T20:54:03Z

Can you share the actual affected certificate? You are unlikely to be hitting the same root cause as no-sct.badssl.com in a unit test, because SCT rules are only enforced for WebPKI certificates.

liggitt · 2022-03-28T20:59:17Z

We only noticed the issue in a unit test checking a cert we expected to be considered invalid (it was a negative test of a cert not signed by a trusted root), so at first we thought we just needed to make the unit test more tolerant of various error messages.

In spelunking around the change in the message, we also ran across https://groups.google.com/g/golang-nuts/c/RGghq2gTWss/m/7GsudTfCAgAJ which indicated requests that previously succeeded were now failing.

Before papering over the change in our unit test by tolerating more validation error messages, I wanted to understand more about which certificates the go validator considers valid that the macOS validator does not. (kubernetes/kubernetes#108956 (comment))

rolandshoemaker · 2022-03-28T23:29:46Z

Apple enforces their SCT requirements on all publicly trusted certificates as part of its base TLS policy (which we use via SecPolicyCreateSSL, since we are generally targeting the web PKI.) Publicly trusted certificates that lack embedded SCTs are very rare, making up something like 0.01% of all publicly trusted certs, but they are out there (the AWS example being probably the most common.)

This will only affect users who are using the bare system certificate pool and are validating certificates which totally lack embedded SCT, with the server providing them via a TLS extension.

It is noted in a TODO in crypto/x509/root_darwin.go that we may want to support passing SCTs passed this way, since we have no way of telling Apple to disable this particular policy (I would need to double check, but it's possible these requirements are not enforced if you use SecPolicyCreateBasicX509, but that would likely also disabled all of the other web PKI policies that we want applied), but how to do that is rather nuanced (since we'd only do anything with them on macOS.)

rolandshoemaker · 2022-03-28T23:49:57Z

Slight side note: the AWS case is a weird one, because I don't think they are sending SCTs at all, despite using publicly trusted certs, so even implementations that know how to pipe SCTs passed via TLS extensions wouldn't work on macOS 🤷.

FiloSottile · 2022-03-29T10:53:57Z

I don't think the SCT policy explains the new error in kubernetes/kubernetes#108956 though, because that's not a publicly trusted certificate. If you want to extract that certificate and share it with us, we can tell you why that one is failing, too.

kubernetes/kubernetes#108956 (comment) papering over the change in our unit test by tolerating more validation error messages, I wanted to understand more about which certificates the go validator considers valid that the macOS validator does not.

We can't really answer this exhaustively, because the macOS verifier has a number of evolving policies that change between OS versions. Note that the platform verifier is only used when the system roots are involved, so behaving like the system is what's expected. I assume k8s clusters use private CAs configured through config.RootCAs for most purposes, which would be unaffected by this.

FiloSottile · 2022-03-29T11:00:21Z

Slight side note: the AWS case is a weird one, because I don't think they are sending SCTs at all, despite using publicly trusted certs, so even implementations that know how to pipe SCTs passed via TLS extensions wouldn't work on macOS 🤷.

Customers should probably reach out to AWS about this. As a short term workaround, it should be possible to add the Amazon root CAs to a x509.SystemCertPool() and use it as config.RootCAs so that the Go verifier is used as well as the system one. (Don't start with an empty pool so that if the root changes you have a chance at not breaking.)

liggitt · 2022-03-29T12:38:46Z

It looks like this change means we no longer get typed TLS errors (e.g. x509.UnknownAuthorityError) when validating using system roots.

That means that special handling of those errors (logging or other fallback paths) that previously worked no longer works in go1.18.

edit: I'll open a separate issue for that, since that is distinct from the "certificate considered valid in go1.17" → "certificate considered invalid in go1.18" issue

liggitt · 2022-03-29T13:07:52Z

opened #52010 for the untyped error issue

liggitt · 2022-03-29T13:10:17Z

I assume k8s clusters use private CAs configured through config.RootCAs for most purposes, which would be unaffected by this.

I also expect that to be true in most scenarios (and in scenarios where it isn't for the certs issued by public CAs to be compatible with system roots, though the referenced AWS issue is evidence that not all certs issued by public CAs are valid).

For k8s' use, I don't think this issue is very significant.

rolandshoemaker · 2022-03-29T15:13:31Z

Oh, that particular test certificate (in TestTLSConfig) is non-compliant in a handful of ways. It's self-signed, but isCA is false, it is missing the cert sign key usage, and it's validity period is likely too long (although I'm not sure if macOS enforces that for self-signed certs.)

calvinbui · 2022-03-30T23:24:39Z

We've had the same issue with connecting to AWS Elasticache Redis servers. Amazon will not support SCTs to avoid publishing customer cluster names in a public log. The connection previously worked fine in 1.17.

jimidle · 2022-03-31T02:35:31Z

A little more background about AWS, or at least how we were connecting to the Neptune graph database service. In case it helps anyone.

Because Neptune is a little "light" on security, you can only connect to it through local/private VPC. This isn't very useful for developers, so we have a VPN to a bastion host for a development only instance of Neptune (Neptune does not have any local installation - it is an AWS service only).

It seems that AWS did not feel the need to put any SCTs in to the Neptune cert, thinking it would only see connections from the secured VPC, and so our connections (via go, it is fine from Java for instance) will fail.

We have raised a ticket with AWS about this. There isn't much can be done about that in Go.

As this is a developer only connection, we have created a reverse proxy with a local CA root. This allows the connection for developers. Hokey, but does what we want for a developer connection. The real solution is of course for AWS to re-issue their certificate, however they say they don't want SCTs in order to avoid placing customer cluster names in a public log (see #51991 (comment) )

bcmills · 2022-04-20T15:24:21Z

This is showing up on the darwin-amd64-10_15 builder as well, though curiously not on any of the other darwin builders.

Marking as release-blocker for Go 1.19 because darwin/amd64 is a first class port.

greplogs --dashboard -md -l -e 'certificate is not standards compliant'

rolandshoemaker · 2022-04-20T16:51:56Z

As far as I can tell this seems, possibly, (this is unbearably painful to diagnose) to be an issue with 10.15.1, which is what the the darwin-amd64-10_15 builder is running. I suspect that updating the builder to use 10.15.6 would fix this, but I have absolutely no clue how viable that is.

bcmills · 2022-04-20T17:32:50Z

I suspect that updating the builder to use 10.15.6 would fix this, but I have absolutely no clue how viable that is.

@golang/release, can you weigh in on that? (How hard is the macOS 10.15 image to update?)

heschi · 2022-04-20T18:44:33Z

For amd64 I think it's maybe a day's work, if we're willing to cut over all the builders at once. Rolling it out gradually will be more unpleasant. I haven't read this issue to judge whether it's a good use of time.

rolandshoemaker · 2022-04-21T15:56:26Z

I don't think there is really any other way to address this issue, given how deeply integrated the TLS client is in the toolchain there isn't really any (safe) way of silently handling/skipping these failures. It's not a high frequency flake though (it seems somewhat correlated with when new certificates are issued) so probably not super high priority.

FiloSottile · 2022-04-21T16:38:59Z

(it seems somewhat correlated with when new certificates are issued)

Can the machine reach the internet? That sounds consistent with a bloom filter window miss on the Apple Valid system, which leads to an OCSP connection to the CA. If that fails, I could see it leading to a vague error like this.

jbg · 2022-05-11T04:38:54Z

In some cases certificates may be deliberately excluded from CT logs to avoid publishing a detailed map of internal infrastructure. (In our case, the certs are associated with DNS names that are only resolvable internally, and which resolve to private IPs.)

e.g. AWS ACM allows disabling CT logging for this purpose, which will result in a valid certificate issued by a trusted CA but not listed in CT logs.

When trying to access a service with such a cert from Go (in our case, using a Terraform provider) on developer (darwin_arm64) machines, we get this certificate is not standards compliant error.

Is there any solution other than logging the certs? Is there any knob in the Go TLS client for turning off the check, which the TF provider could provide a config option to turn?

jimidle · 2022-05-11T04:57:35Z

In our case, we were just needing developers to access a development version of Neptune on AWS. We were doing that with a bastion host and ssh. The Neptune cert is set up exactly as you say, to avoid public logs for what is intended to be a system accessed from a VPC in AWS. We therefore wrote a small reverse proxy instead of a simple tunnel. That works for our case as our code runs in the VPC as AWS intend, other than for developers. As I understand it from the comments here, Go 1.19 will try to address this, but I cannot speak for the Go development team of course.

…

On May 11, 2022 at 12:39:06 PM, Jasper ***@***.***> wrote: In some cases certificates may be deliberately excluded from CT logs to avoid publishing a detailed map of internal infrastructure. e.g. AWS ACM allows disabling CT logging for this purpose, which will result in a valid certificate issued by a trusted CA but not listed in CT logs. When trying to access a service with such a cert from Go (in our case, using a Terraform provider) on developer (darwin_arm64) machines, we get this certificate is not standards compliant error. Is there any solution other than logging the certs? Is there any knob in the Go TLS client for turning off the check, which the TF provider could provide a config option to turn? — Reply to this email directly, view it on GitHub <#51991 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJ7TMBSJBB4IPNDNOYUWPLVJM2WVANCNFSM5R4DNYCQ> . You are receiving this because you commented.Message ID: ***@***.***>

thefallentree · 2022-08-16T17:04:19Z

Hello:

i can confirm that Amazon Neptune is affected :

 {"error": "x509: "*.xxxxxx.us-east-1.neptune.amazonaws.com" certificate is not standards compliant"}

what is the current recommend workaround?

melaraj2 · 2022-09-11T02:44:23Z

Amazon Elastic Cache Redis is affected as well.
x509: “*.testredis.3myxt2.use1.cache.amazonaws.com” certificate is not standards compliant

mkoese · 2022-09-16T07:56:41Z

OpenShift Client 4.11.4 is affected as well.

oc login --token=sha256~xxx --server=https://api.xx.com
error: x509: “api.xx.com” certificate is not standards compliant

I just downgraded the OpenShift Client to 4.10.22 now it is working again.

…1991

…lang/go#51991

ropnop · 2022-09-16T18:10:18Z

Commenting to follow along - I started seeing CMS/PKS7 signatures failing on Darwin amd64 that use Digicert's RFC3161 Timestamp Server (http://timestamp.digicert.com)

error validating signature error=invalid signature for "test.txt": x509: “DigiCert Timestamp 2022 - 2” certificate is not standards compliant

I was able to manually work around by fetching the Digicert TS Crt from https://knowledge.digicert.com/content/dam/digicertknowledgebase/DigiCertTrustedRootG4.crt and adding it to an x509.Pool to pass in for verification

workaround: golang/go#51991

AaronFriel · 2022-12-12T23:18:52Z

Pulumi had an internal user encounter this issue making requests to get.pulumi.com, served by Amazon CloudFront. The certificate for CloudFront had recently been rotated on Friday, Dec 9. They observed the issue on macOS 11.6, and upon restarting and updating to 11.7, the issue appeared to be resolved.

We're still keeping an eye on this. Has anyone else seen this behavior on Big Sur (11.x) and resolved by a patch release between 11.6 and 11.7?

Alternatively, does anyone know if the updates to the macOS system are resolving the issue, or is the update clearing some cached state that would cause it to reoccur on the next certificate rotation?

davidwallacejackson · 2022-12-26T07:20:55Z

Pulumi had an internal user encounter this issue making requests to get.pulumi.com, served by Amazon CloudFront. The certificate for CloudFront had recently been rotated on Friday, Dec 9. They observed the issue on macOS 11.6, and upon restarting and updating to 11.7, the issue appeared to be resolved.

We're still keeping an eye on this. Has anyone else seen this behavior on Big Sur (11.x) and resolved by a patch release between 11.6 and 11.7?

Alternatively, does anyone know if the updates to the macOS system are resolving the issue, or is the update clearing some cached state that would cause it to reoccur on the next certificate rotation?

If this is helpful, I just saw this error trying to connect to a GKE cluster from MacOS 12.3.1, so I assume it was clearing the cache that did it. Incidentally, if there's a way to manually do this without updating the OS, it'd be useful to know as a workaround!

stravag · 2023-01-11T14:38:46Z

For anyone struggling with this issue. I had the same problem:

package main

import (
	"log"
	"net/http"
	"os"
)

func main() {
	res, err := http.Get("https://charts.bitnami.com/bitnami/index.yaml")
	if err != nil {
		log.Fatal(err)
	}
	res.Write(os.Stdout)
}

go run <file-above>.go with version >= 1.18 lead to the mentioned certificate is not standards compliant error. It worked fine with 1.17.

Upgrading macOS Monterrey from 12.5 to 12.6.2 solved the issue for me!! It also seems to work with macOS 13 Ventura. I can now run the above program just fine with go version 1.19

jameskilroe · 2023-02-15T18:46:22Z

I am using go version go1.20.1 darwin/arm64 and MacOS Version 13.2.1 (22D68) and this issue is now occurring when I use github.com/gorilla/websocket .Dial() function.

The error is : tls: failed to verify certificate: x509: “*.exchange.coinbase.com” certificate is not standards compliant"

When is this scheduled to be resolved? Is there any simple workaround if accessing a public site where one has no control over the certificate?

Any help greatly appreciated!

AaronFriel · 2023-02-15T20:30:23Z

@jameskilroe hey! we at Pulumi dug deep into this after seeing a similar issue. You should be able to resolve it by restarting your machine. We found that should almost always fix the issue.

Workaround

We found that in every case where a user reported this issue, either of these were true:

The machine either had been recently reimaged, and not rebooted since.
The user had not restarted the machine in a substantial period of time.

In both cases, restarting the OS was the workaround.

Analysis

I'm going to summarize my colleague @kmosher's analysis. In recent years Apple, Google, and others have added the following requirements for a TLS cert to be considered valid
:

It must be valid for no longer than 398 days
It must be signed by multiple Certificate Transparency (CT) logs

On macOS, and in Safari and Go programs, the system service trustd is responsible for checking a certificate against certificate transparency (CT) log information cached by the OS.

Due to unknown reasons, trustd does not update the list of trusted certificate transparency (CT) logs it uses while the system is running. As a result, certificates signed against chains that are currently trusted (and may be listed in the file below) aren't considered valid until a restart.

The trusted certificate transparency logs on macOS can be located here:

/System/Library/Security/Certificates.bundle/Contents/Resources/TrustedCTLogs.plist

And Apple publishes a JSON document for the OS to update from here:

https://valid.apple.com/ct/log_list/current_log_list.json

AaronFriel · 2023-02-15T20:34:26Z

@rsc, @ianlancetaylor: Based on the above, I believe this issue can be closed - or perhaps moved to a Discussion with an accepted answer. I believe that someone should file a report with Apple's bug reporting tool Feedback Assistant to resolve this behavior with macOS if it hasn't been. This issue may already be fixed and released, but as we describe above, users who encounter the issue are likely to be on out of date machines that have not updated or even restarted their machine recently.

jameskilroe · 2023-02-16T09:26:16Z

Hi @AaronFriel

Thanks for the answer. I updated my machine to the latest OS to try and solve the problem and did restart my machine a few time this morning, but unfortunately, the problem persists.

I did notice that the files in my TrustedCTLogs.plist were last updated on 9 Feb (before my update). Is there any chance you know how to force and update? I did some googling but no obvious answers.

All round very frustrating!

jbg · 2023-02-16T09:34:48Z

@jameskilroe rather than looking at the date, diff it against the current list (https://valid.apple.com/ct/log_list/current_log_list.json). The set of valid CT logs doesn't change that often (last change 15 Jan). If you have the latest list and have rebooted recently, then you may have a different issue (like the certificate is not actually present in the CT logs — you can check this — or is valid for too long).

Clients that rely on OSX APIs for certificate validation may find an error with the message "certificate is not standards compliant" with certificates that don't comply with Apple rules for certificate validation. When this error happens, the actual reason for each certificate is not exposed, and it seems to happen with certificates that should be valid in the context of the validation. More discussion about this can be found in golang/go#51991. This happens with certificates generated by `elastic-package`, clients sometimes report this error with configurations that otherwise should accept these certificates. According to this post, one of the rules is that certificates cannot be valid for more than 825 days. https://rahulkj.github.io/openssl,/certificates/2022/09/09/self-signed-certificates.html Reduce the expiration time to try to reduce the chances of triggering this error.

dims mentioned this issue Mar 28, 2022

go1.18: tls unit tests don't pass locally kubernetes/kubernetes#108956

Closed

seankhliao added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Mar 28, 2022

liggitt mentioned this issue Mar 29, 2022

crypto/x509: go1.18 stops returning typed errors when using system roots on darwin #52010

Closed

apparentlymart mentioned this issue Apr 1, 2022

Build official releases with Go 1.18 hashicorp/terraform#30768

Merged

bcmills changed the title ~~crypto/x509: "certificate is not standards compliant" on MacOS only with golang 1.18~~ crypto/x509: "certificate is not standards compliant" on MacOS Apr 20, 2022

bcmills added OS-Darwin release-blocker labels Apr 20, 2022

bcmills added this to the Go1.19 milestone Apr 20, 2022

na-- mentioned this issue Aug 9, 2022

The document is not clear for calling https grafana/k6#2642

Open

iseki-working pushed a commit to murphysecurity/murphysec that referenced this issue Sep 16, 2022

chore: IsTlsCertError doesn't work on macOS because of: golang/go#5…

6baac83

…1991

iseki-working pushed a commit to murphysecurity/murphysec that referenced this issue Sep 16, 2022

fix(workaround): IsTlsCertError Workaround for macOS because of: go…

be9930b

…lang/go#51991

iseki-working pushed a commit to murphysecurity/murphysec that referenced this issue Sep 16, 2022

fix(workaround): IsTlsCertError Workaround for macOS because of: go…

a9c9e25

…lang/go#51991

bkessler-go assigned rolandshoemaker Oct 17, 2022

blancharda mentioned this issue Nov 16, 2022

unable to create a zarf package containing images from a registry with a self-signed certificate defenseunicorns/zarf#1015

Closed

iseki0 added a commit to murphysecurity/murphysec that referenced this issue Nov 21, 2022

feat: infra/tlserr

4ee3c4a

workaround: golang/go#51991

iseki0 added a commit to murphysecurity/murphysec that referenced this issue Dec 1, 2022

feat: infra/tlserr

d3b2857

workaround: golang/go#51991

janaka mentioned this issue Dec 13, 2022

AWS API Gateway create issue - “apigateway.eu-west-1.amazonaws.com” certificate is not standards compliant pulumi/pulumi-aws-apigateway#69

Open

pdf mentioned this issue Dec 21, 2022

helm repo add bitnami gives not a valid chart repository or cannot be reached: stream error: stream ID 1; INTERNAL_ERROR bitnami/charts#8433

Closed

gopherbot modified the milestones: Go1.20, Go1.21 Feb 1, 2023

rolandshoemaker mentioned this issue Feb 2, 2023

crypto/x509: support SCT/OCSP passthrough when using platform verifiers #58251

Open

ukane-philemon mentioned this issue Feb 15, 2023

client/comms: check for non-standard compliant error decred/dcrdex#2130

Merged

jsoriano mentioned this issue Feb 15, 2023

Reduce expiration time of certificates elastic/elastic-package#1146

Merged

t-botz mentioned this issue Feb 18, 2023

"certificate is not standards compliant" on Mac with custom CA hashicorp/boundary#2988

Closed

disq mentioned this issue Mar 6, 2023

Support for AWS Neptune as a Graph DB destination cloudquery/cloudquery#6800

Closed

crypto/x509: "certificate is not standards compliant" on MacOS #51991

crypto/x509: "certificate is not standards compliant" on MacOS #51991

dims commented Mar 28, 2022

dims commented Mar 28, 2022

seankhliao commented Mar 28, 2022

FiloSottile commented Mar 28, 2022

liggitt commented Mar 28, 2022 •

edited

rolandshoemaker commented Mar 28, 2022

rolandshoemaker commented Mar 28, 2022

FiloSottile commented Mar 29, 2022

FiloSottile commented Mar 29, 2022

liggitt commented Mar 29, 2022 •

edited

liggitt commented Mar 29, 2022

liggitt commented Mar 29, 2022

rolandshoemaker commented Mar 29, 2022

calvinbui commented Mar 30, 2022

jimidle commented Mar 31, 2022 •

edited

bcmills commented Apr 20, 2022

rolandshoemaker commented Apr 20, 2022

bcmills commented Apr 20, 2022

heschi commented Apr 20, 2022

rolandshoemaker commented Apr 21, 2022

FiloSottile commented Apr 21, 2022

jbg commented May 11, 2022 •

edited

jimidle commented May 11, 2022 via email

thefallentree commented Aug 16, 2022

melaraj2 commented Sep 11, 2022

mkoese commented Sep 16, 2022

ropnop commented Sep 16, 2022

AaronFriel commented Dec 12, 2022 •

edited

davidwallacejackson commented Dec 26, 2022

stravag commented Jan 11, 2023 •

edited

jameskilroe commented Feb 15, 2023

AaronFriel commented Feb 15, 2023 •

edited

AaronFriel commented Feb 15, 2023

jameskilroe commented Feb 16, 2023

jbg commented Feb 16, 2023

crypto/x509: "certificate is not standards compliant" on MacOS #51991

crypto/x509: "certificate is not standards compliant" on MacOS #51991

Comments

dims commented Mar 28, 2022

What version of Go are you using (go version)?

Does this issue reproduce with the latest release?

What operating system and processor architecture are you using (go env)?

What did you do?

What did you expect to see?

What did you see instead?

dims commented Mar 28, 2022

seankhliao commented Mar 28, 2022

FiloSottile commented Mar 28, 2022

liggitt commented Mar 28, 2022 • edited

rolandshoemaker commented Mar 28, 2022

rolandshoemaker commented Mar 28, 2022

FiloSottile commented Mar 29, 2022

FiloSottile commented Mar 29, 2022

liggitt commented Mar 29, 2022 • edited

liggitt commented Mar 29, 2022

liggitt commented Mar 29, 2022

rolandshoemaker commented Mar 29, 2022

calvinbui commented Mar 30, 2022

jimidle commented Mar 31, 2022 • edited

bcmills commented Apr 20, 2022

rolandshoemaker commented Apr 20, 2022

bcmills commented Apr 20, 2022

heschi commented Apr 20, 2022

rolandshoemaker commented Apr 21, 2022

FiloSottile commented Apr 21, 2022

jbg commented May 11, 2022 • edited

jimidle commented May 11, 2022 via email

thefallentree commented Aug 16, 2022

melaraj2 commented Sep 11, 2022

mkoese commented Sep 16, 2022

ropnop commented Sep 16, 2022

AaronFriel commented Dec 12, 2022 • edited

davidwallacejackson commented Dec 26, 2022

stravag commented Jan 11, 2023 • edited

jameskilroe commented Feb 15, 2023

AaronFriel commented Feb 15, 2023 • edited

Workaround

Analysis

AaronFriel commented Feb 15, 2023

jameskilroe commented Feb 16, 2023

jbg commented Feb 16, 2023

What version of Go are you using (`go version`)?

What operating system and processor architecture are you using (`go env`)?

liggitt commented Mar 28, 2022 •

edited

liggitt commented Mar 29, 2022 •

edited

jimidle commented Mar 31, 2022 •

edited

jbg commented May 11, 2022 •

edited

AaronFriel commented Dec 12, 2022 •

edited

stravag commented Jan 11, 2023 •

edited

AaronFriel commented Feb 15, 2023 •

edited