starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[PR #2802] [MERGED] Update SignConfig to use SHA2 variant per governance request. #25080

New Issue
Open
opened 2026-01-31 09:07:10 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 09:07:10 +00:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/microsoft/terminal/pull/2802
Author: @miniksa
Created: 9/18/2019
Status: ✅ Merged
Merged: 9/19/2019
Merged by: @miniksa

Base: master ← Head: user/miniksa/colortool_signing

📝 Commits (1)

  • c854bb0 Update SignConfig to use SHA2 variant per governance request.

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 src/tools/ColorTool/signing/SignConfig.xml (+1 -1)

📄 Description

Summary of the Pull Request

We've been requested to move to SHA2 certificates where possible. This replaces the friendly name that internally converts to a variant containing a non-zero amount of SHA1 stuff into one that is fully SHA2.

PR Checklist

  • Closes internal mail notification
  • I work here
  • I have to change the code to test the build and wait for the job authorization to update. Unfortunately because the signed builds are triggered by an authorized person, I'll have to do it manually once this is in. I cannot auto-trigger a signed build in a PR.
  • Docs for signing are available in the existing Engineering System wiki pages.
  • I'm a core contributor

Detailed Description of the Pull Request / Additional comments

This literally just replaces the friendly name for the old certificate with the one for the new certificate so the signing tool knows which cert to pick up out of the certificate store. It has to dovetail with the authorization which I've already submitted for review.

Validation Steps Performed

As I mentioned above, I can't validate it until it's in and the authorization is approved. I'll manually launch a signed build and check it out (and maybe even release it) once we're all authorized and updated.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/microsoft/terminal/pull/2802 **Author:** [@miniksa](https://github.com/miniksa) **Created:** 9/18/2019 **Status:** ✅ Merged **Merged:** 9/19/2019 **Merged by:** [@miniksa](https://github.com/miniksa) **Base:** `master` ← **Head:** `user/miniksa/colortool_signing` --- ### 📝 Commits (1) - [`c854bb0`](https://github.com/microsoft/terminal/commit/c854bb0ddaa2612b199dad63a51a29ba48eb6d55) Update SignConfig to use SHA2 variant per governance request. ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/tools/ColorTool/signing/SignConfig.xml` (+1 -1) </details> ### 📄 Description <!-- Enter a brief description/summary of your PR here. What does it fix/what does it change/how was it tested (even manually, if necessary)? --> ## Summary of the Pull Request We've been requested to move to SHA2 certificates where possible. This replaces the friendly name that internally converts to a variant containing a non-zero amount of SHA1 stuff into one that is fully SHA2. <!-- Please review the items on the PR checklist before submitting--> ## PR Checklist * [X] Closes internal mail notification * [X] I work here * [X] I have to change the code to test the build and wait for the job authorization to update. Unfortunately because the signed builds are triggered by an authorized person, I'll have to do it manually once this is in. I cannot auto-trigger a signed build in a PR. * [X] Docs for signing are available in the existing Engineering System wiki pages. * [X] I'm a core contributor <!-- Provide a more detailed description of the PR, other things fixed or any additional comments/features here --> ## Detailed Description of the Pull Request / Additional comments This literally just replaces the friendly name for the old certificate with the one for the new certificate so the signing tool knows which cert to pick up out of the certificate store. It has to dovetail with the authorization which I've already submitted for review. <!-- Describe how you validated the behavior. Add automated tests wherever possible, but list manual validation steps taken as well --> ## Validation Steps Performed As I mentioned above, I can't validate it until it's in and the authorization is approved. I'll manually launch a signed build and check it out (and maybe even release it) once we're all authorized and updated. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
claunia added the pull-request label 2026-01-31 09:07:10 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#25080
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?