There is work in bug 1366237 to add new public keys for the releng accounts. We'll also need to add ffxbld public key to the releng Github account. However, I don't have access to the required credentials to do that.
@Chris: any idea who could help with this?
I can probably help. I'm curious, what is the ffxbld key required for on github?
(In reply to Chris AtLee [:catlee] from comment #2) > I can probably help. > > I'm curious, what is the ffxbld key required for on github? Well, I don't know about that. ni-ing Callek since he's the one that did the change last time.
I'm not *certain* either, offhand I think it was for vcs-sync, and for partner-repack needs.
The ffxbld key should NOT be used by vcs-sync. That would be a bug. I believe the ffxbld key is used to clone/fetch private repos from mozilla-partners for partner repack needs. I.e. the new key needs to be added, and the old key removed, on the same timetable as the keys in ldap. (I don't see a "remove from ldap" bug yet.)
Both https://github.com/moz-releng-automation and https://github.com/moz-v2v-gh have access to the mozilla-partners repo.
The new key has been added to the moz-releng-automation account.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.