Re:Writing secure Go code
by superb_dev on Monday November 04, 2024 @04:08PM
(#42045998)
The examples in that ticket are convoluted, who would write code like that? Has this issue been spotted in the wild?
I agree that there is some issue and a lint should probably warn you about these, but I doubt a lot of people will run into it.
You should read that article carefully.
Some Go core team members don't agree with you: https://github.com/golang/go/issues/66156
you're literally the only person who's making a mountain out of a molehill coming up with ever more convoluted code to "prove" the change was a bad thing.
It indeed is. Please read https://go101.org/blog/2024-03-01-for-loop-semantic-changes-... and https://github.com/golang/go/issues/66156
a lot of words and yet no real world issues identified
The problems are right there. But some people choose to turn a blind eye.
Re:Writing secure Go code
by candiddevmike on Monday November 04, 2024 @02:46PM
(#42045340)
.0 is for local development, .1+ is for production
There might be some bugs in .2: https://github.com/golang/go/issues/70035
Re:Writing secure Go code
by 01119288523 on Monday November 04, 2024 @04:58PM
(#42046401)
Good grief, you're still banging on about this. It's been well over a year. Literally no one agrees with you. That happens sometimes. But please, accept that and give it a rest already.
> The second step is to keep the Go versions in our projects current. Even though we don’t use the latest and greatest language features, bumping the Go version gives us all security patches for discovered vulnerabilities.
It is not always a good strategy to use the latest toolchain version. There are often some fresh bugs in it. From the security perspective, it is better to use the previous version, which is also still being maintained.