-
Notifications
You must be signed in to change notification settings - Fork 349
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
Tracking: Update to new .NET cert in repos #7348
Comments
/cc @blowdart |
[Async Triage] This seems to be something @mmitche is driving and already in flight, so adding to the "Tracking" epic to get off triage. |
I'd rather have this work be part of a proper epic if at all possible. @mmitche - hopefully the security work has enough "shape" to at least get an epic started? |
@markwilkie I don't think it's in that shape yet. There is a grab bag of security-ish related items at this point (e.g. using a different storage account for builds), but as of yet no real business goal except "we should have a secure engineering system". That box is essentially uncheckable (how do you know?), and is much larger than a single epic's scope anyway. Lastly, changing the cert doesn't have to do with the security of the engineering system, it's more for product security and customer choices (see dotnet/announcements#184). We could make this its own epic. What do you think? |
Added a placeholder epic and added this issue to it. |
Donezo |
Are details of this new certificate available? I can't find the thumbprint or subject name, or those of the issuing certificate, either here or over on dotnet/announcements#184 |
Tracking the update to the new cert in the repos
https://github.com/dotnet/arcade/pull/7347/files - support for UseDotNetCertificate
The text was updated successfully, but these errors were encountered: