Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gosec: exclude G601 and G113 #4736

Closed
wants to merge 1 commit into from
Closed

Conversation

ldez
Copy link
Member

@ldez ldez commented May 21, 2024

Temporary fix.

Related to #4735

@ldez ldez added bug Something isn't working linter: update Update the linter implementation inside golangci-lint labels May 21, 2024
@ldez ldez added this to the next milestone May 21, 2024
@@ -179,17 +166,35 @@ func convertGosecGlobals(globalOptionFromConfig any, conf gosec.Config) {
func gosecRuleFilters(includes, excludes []string) []rules.RuleFilter {
var filters []rules.RuleFilter

if len(includes) > 0 {
filters = append(filters, rules.NewRuleFilter(false, includes...))
cleanIncludes := cleanRules(includes)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we really remove the possibility to enable them even if a user wants to? I get we remove them from default rules if no config is provided but if explicitly enabled by a config I would expect them to be enabled, the extra time isn't necessarily a blocker for everyone.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the extra time isn't necessarily a blocker for everyone.

We are talking about a duration multiplied by at least 4 (milliseconds becomes seconds).

Should we really remove the possibility to enable them even if a user wants to?

We cannot really play with "default" because the current problem impacts users who already explicitly enable those rules.

This fix is a temporary fix, we will create the real fix when gosec allows us to handle the Go version.

Copy link
Member Author

@ldez ldez May 21, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you feel uncomfortable with this PR, we can downgrade to v2.19.0.
But technically, the v2.19.0 contains a bug with how to handle the Go version on the same rules.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are talking about a duration multiplied by at least 4 (milliseconds becomes seconds).

Yeah I saw your table but to me 10s isn't a blocker in my CI e.g. so if I was using this check I would be annoyed it wasn't up to me to opt in.

This fix is a temporary fix, we will create the real fix when gosec allows us to handle the Go version.

Got that, I guess it's not the end of the world and for people who reeeally care they can probably stick to an older version of golangci-lint.

@ldez
Copy link
Member Author

ldez commented May 25, 2024

Supersedes by #4748

@ldez ldez closed this May 25, 2024
@ldez ldez added the declined label May 25, 2024
@ldez ldez deleted the fix/gosec-temp branch May 25, 2024 13:21
@ldez ldez modified the milestones: next, v1.59 May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working declined linter: update Update the linter implementation inside golangci-lint
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants