From dbba35d85a9ea34dcf9655754d97cd58687b2dec Mon Sep 17 00:00:00 2001 From: Roland Bracewell Shoemaker Date: Mon, 4 Mar 2024 16:07:24 -0800 Subject: [PATCH] [golang] restrict access to golang issues (#11663) We've had multiple security reports originating from crashes discovered by oss-fuzz. I was unaware that the results were entirely public. Restrict access to issues to the Go Security team. **Note:** It's unclear to me if this actually accomplishes what I want. `view_restrictions` seems entirely undocumented. From contextual clues from other projects it _seems_ that removing the field causes restriction, but that is entirely a guess. --- projects/golang/project.yaml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/projects/golang/project.yaml b/projects/golang/project.yaml index 69ea96862..cd1d794d7 100644 --- a/projects/golang/project.yaml +++ b/projects/golang/project.yaml @@ -1,13 +1,13 @@ homepage: "https://golang.org/" main_repo: "https://github.com/golang/go" -primary_contact: "golang-fuzz@googlegroups.com" +primary_contact: "security@golang.org" auto_ccs: - - "emmanuel@orijtech.com" + - "bracewell@google.com" + - "dneil@google.com" + - "tatianabradley@google.com" - "Adam@adalogics.com" - - "cuong.manhle.vn@gmail.com" language: go sanitizers: - address fuzzing_engines: - libfuzzer -view_restrictions: none