Re: [go-nuts] Re: [security] Go 1.18.1 and Go 1.17.9 pre-announcement

golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/856fcb34-c7ed-4dca-aab6-c42001492d93n%40googlegroups.com > <https://groups.google.com/d/msgid/golang-nuts/856fcb34-c7ed-4dca-aab6-c42001492d93n%40googlegroup

Re: [go-nuts] Changes to x509 in Go 1.18

d an > email to golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/CAGPPfg-PtW7dqeNKo72fvLsLZ1Qg2i_AwmUBJcTGMNgeHUhfCA%40mail.gmail.com > <https://groups.google.com/d/msgid/golang-nuts/CAGPPfg-PtW7dqeNKo

Re: [go-nuts] Changes to x509 in Go 1.18

I quote the ticket you raised, in case it is useful to others: > > https://github.com/golang/go/issues/51991 > > > On Mar 29, 2022 at 2:48:34 AM, Davanum Srinivas wrote: > >> Jim, >> >> Looks like we ended up seeing the same problem in a kubernetes test case >