Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.

Use MicrosoftSHA2 for DAC signing #27933

Merged
merged 2 commits into from
Nov 25, 2019

Conversation

hoyosjs
Copy link
Member

@hoyosjs hoyosjs commented Nov 23, 2019

The DAC can't be signed with a 400 cert like all other DLLs. There's a requirement to have a dual Sha signature for Watson scenarios.

@hoyosjs hoyosjs force-pushed the juhoyosa/fix-2.1-dacsign branch from b2c67a3 to 63d53ef Compare November 23, 2019 21:55
@hoyosjs hoyosjs requested review from mmitche and mikem8361 November 23, 2019 23:17
@hoyosjs
Copy link
Member Author

hoyosjs commented Nov 23, 2019

After this both crossarch and regular DAC request for MicrosoftSHA2 signatures.

image

Copy link
Member

@mikem8361 mikem8361 left a comment

Choose a reason for hiding this comment

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

Looks good. Thanks!

@mmitche mmitche merged commit 38cc993 into dotnet:release/2.1 Nov 25, 2019
mmitche pushed a commit that referenced this pull request Nov 25, 2019
* Update CoreClr, CoreFx to servicing-28207-04, servicing-28208-01, respectively (#27899)

* update branding for 2.1 (#27914)

* Fix GetSequencePoints when profiler provides mapping via SetILInstrumentedCodeMap (#27295)

Port #25802 to release/2.1

* Use MicrosoftSHA2 for DAC signing (#27933)

* Use MicrosoftSHA2 for DAC signing

* Fix DAC name
@hoyosjs hoyosjs deleted the juhoyosa/fix-2.1-dacsign branch June 29, 2021 17:11
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants