Dear all,

On Sat Sep 5, 2026 at 10:53 CEST, Andrew Lee (李健秋) wrote:
> While porting goxkcdpwgen from experimental to unstable. I noticed the
> legacy DefaultGODEBUG flags are still appears in the built binary.

I got the impression, that the older the go release in go.mod is, the
longer is the debug list. Please note, this is an impression and I did
no thorough investigation. But maybe we build in an compatibility mode
which does not use all 1.27 options when go.mod says e.g. 1.25.

Two examples:

- privatebin-ci:
        - go.mod is `go 1.26`
        - `DefaultGODEBUG=tracebacklabels=0,x509sslcertoverrideplatform=0`
- ymuse
        - go.mod is `go 1.21`
        - 
`DefaultGODEBUG=containermaxprocs=0,cryptocustomrand=1,decoratemappings=0,gotestjsonbuildtext=1,httpcookiemaxnum=0,httplaxcontentlength=1,httpmuxgo121=1,httpservecontentkeepheaders=1,multipathtcp=0,randseednop=0,rsa1024min=0,tlsmlkem=0,tlssecpmlkem=0,tlssha1=1,tracebacklabels=0,updatemaxprocs=0,urlmaxqueryparams=0,urlstrictcolons=0,winreadlinkvolume=0,winsymlink=0,x509negativeserial=1,x509rsacrt=0,x509sha256skid=0,x509sslcertoverrideplatform=0,x509usepolicies=0`

Best regards,
Martin

Attachment: signature.asc
Description: PGP signature

Reply via email to