1349425 - project Acorn

Status: RESOLVED WONTFIX

(Release Engineering :: General, enhancement, P1)

Description

[Jordan Lund (:jlund)]

after the recent reorg, now might seem like the perfect opportunity to do some spring security cleaning.

At a high level this would involve:


1) figure out a definitive manifest of who has what, where and why.
2) standardize how the manifest gets updated through a defined spec
3) scrubbing secrets and permissions for individuals who no longer require such keys

(2) will be the hardest part as a lot of the maintenance and diligence will rely on team culture and acceptance.

I see this manifest/spec as something that lives within a repo, possibly along side our private repo. And when permissions are requested from within releng, the initial step is opening an issue in that repo prior to say balrog or puppet.

Finally, why Acorn? Because releng likes squirrels and when I imagine a squirrel trying to keep track of all its precious nuts that it has scattered and buried in various safe hidings, I think of the challenge we have keeping track of all our keys.

Comment 1

[Jordan Lund (:jlund)]

bug 1353530 could provide good history/context into current state of things

Comment 2

[Aki Sasaki (not active)]

Backlog cleanup.