Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore: update azure certs#21265

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
code-asher merged 1 commit intomainfromasher/update-azure-certs
Dec 15, 2025
Merged

chore: update azure certs#21265

code-asher merged 1 commit intomainfromasher/update-azure-certs
Dec 15, 2025

Conversation

@code-asher
Copy link
Member

@code-ashercode-asher commentedDec 15, 2025
edited
Loading

Some of these certs expired earlier this year, but I have left them in because I am still not sure I understand the impact or how to test.

We got a notice saying there are new sub-CAs so I went ahead and added all the "issuing" ones but I am not 100% sure this is correct. The documentation is not explicit about which certificates are necessary for signature verification.

@kylecarbs would you happen to have additional context? In thePR the ECC ones were not added and of the RSA ones only thexsign variant was included, is that all we need?

Closescoder/internal#1147

Edit: decided to add just the ECCxsign variants (RSA ones were already bundled). We think these are probably the ones we need (the public key is the same as the non-xsign variants). However these certs do expire in August, so likely they will need to be replaced soon...

@code-ashercode-asherforce-pushed theasher/update-azure-certs branch 3 times, most recently from249257d to3afdf39CompareDecember 15, 2025 21:44
Copy link
Member

@EmyrkEmyrk left a comment

Choose a reason for hiding this comment

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

Readinghttps://learn.microsoft.com/en-us/azure/security/fundamentals/azure-ca-details?tabs=root-and-subordinate-cas-list, I think@code-asher's take makes sense.

It seems some RSA certs were replaced by ECC, and why there are more now.

I think we need to actually test this with some azure instances, and we have to test it after January 6 according to the blog post.

Since no certs are remove, I will approve.
@code-asher can we create an issue to test said certs against a vm after Jan 6?

@code-asher
Copy link
MemberAuthor

Openedcoder/internal#1198 so we can test after 1/6.

@code-ashercode-asher merged commit871ed12 intomainDec 15, 2025
30 checks passed
@code-ashercode-asher deleted the asher/update-azure-certs branchDecember 15, 2025 22:44
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsDec 15, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.

Reviewers

@EmyrkEmyrkEmyrk approved these changes

Assignees

@code-ashercode-asher

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Investigate whether we need to upgrade Azure instance ID certs

3 participants

@code-asher@Emyrk

[8]ページ先頭

©2009-2025 Movatter.jp