News for hackers. Stuff that matters.
Re:Writing secure Go code by tapirl on Monday November 04, 2024 @01:52PM (#42044837)
Please note, currently, there are no tools to detect the new footguns created by the new semantics of 3-clause "for;;" loops: https://github.com/golang/go/issues/66156

> 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.

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.

Re:Writing secure Go code by tapirl on Tuesday November 05, 2024 @02:15AM (#42049311)
You should read that article carefully.

Some Go core team members don't agree with you: https://github.com/golang/go/issues/66156

Re:Writing secure Go code by arccy on Monday November 04, 2024 @02:09PM (#42044982)
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.
Re:Writing secure Go code by tapirl on Monday November 04, 2024 @02:22PM (#42045112)
Re:Writing secure Go code by arccy on Monday November 04, 2024 @02:52PM (#42045401)
a lot of words and yet no real world issues identified
Re:Writing secure Go code by tapirl on Monday November 04, 2024 @03:02PM (#42045485)
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
Re:Writing secure Go code by tapirl on Monday November 04, 2024 @03:00PM (#42045461)
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)
Re:Writing secure Go code by arp242 on Monday November 04, 2024 @06:01PM (#42046965)
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.
Re:Writing secure Go code by tapirl on Tuesday November 05, 2024 @02:11AM (#42049290)
Copernicus was in the same position.

:)