Skip to content
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

[release/7.0-rc1] Do not attempt to sign .cat files #190

Merged
merged 1 commit into from
Aug 23, 2022

Conversation

mmitche
Copy link
Member

@mmitche mmitche commented Aug 23, 2022

.cat files cannot be dual signed. However, there was a bug in signtool.exe where an attempt to add a second signature did not fail, and instead corrupted the cat file. Validation steps were added in the signing process to avoid this situation, and this broke builds.

.cat files cannot be dual signed. However, there was a bug in signtool.exe where an attempt to add a second signature did not fail, and instead corrupted the cat file. Validation steps were added in the signing process to avoid this situation, and this broke builds.
@mmitche mmitche changed the title Do not attempt to sign .cat files [release/7.0-rc1] Do not attempt to sign .cat files Aug 23, 2022
@lewing lewing enabled auto-merge (squash) August 23, 2022 18:44
@lewing lewing merged commit 321399a into release/7.0-rc1 Aug 23, 2022
mmitche added a commit to mmitche/emsdk that referenced this pull request Aug 23, 2022
.cat files cannot be dual signed. However, there was a bug in signtool.exe where an attempt to add a second signature did not fail, and instead corrupted the cat file. Validation steps were added in the signing process to avoid this situation, and this broke builds.
mmitche added a commit to mmitche/emsdk that referenced this pull request Aug 23, 2022
.cat files cannot be dual signed. However, there was a bug in signtool.exe where an attempt to add a second signature did not fail, and instead corrupted the cat file. Validation steps were added in the signing process to avoid this situation, and this broke builds.
@lewing lewing deleted the mmitche-patch-1 branch August 23, 2022 20:53
lewing added a commit to lewing/emsdk that referenced this pull request Aug 24, 2022
commit 5ef6613
Author: Matt Mitchell <[email protected]>
Date:   Wed Aug 24 09:22:40 2022 -0700

    Explicitly avoid signing python.cat (dotnet#192)

    Set the python.cat signature to None so that tooling doesn't complain about not having a signature mapping for this file.

commit 321399a
Author: Matt Mitchell <[email protected]>
Date:   Tue Aug 23 11:51:37 2022 -0700

    Do not attempt to sign .cat files (dotnet#190)

    .cat files cannot be dual signed. However, there was a bug in signtool.exe where an attempt to add a second signature did not fail, and instead corrupted the cat file. Validation steps were added in the signing process to avoid this situation, and this broke builds.
lewing added a commit that referenced this pull request Aug 24, 2022
commit 5ef6613
Author: Matt Mitchell <[email protected]>
Date:   Wed Aug 24 09:22:40 2022 -0700

    Explicitly avoid signing python.cat (#192)

    Set the python.cat signature to None so that tooling doesn't complain about not having a signature mapping for this file.

commit 321399a
Author: Matt Mitchell <[email protected]>
Date:   Tue Aug 23 11:51:37 2022 -0700

    Do not attempt to sign .cat files (#190)

    .cat files cannot be dual signed. However, there was a bug in signtool.exe where an attempt to add a second signature did not fail, and instead corrupted the cat file. Validation steps were added in the signing process to avoid this situation, and this broke builds.
lewing added a commit that referenced this pull request Sep 8, 2022
* Do not attempt to sign .cat files (#190)

.cat files cannot be dual signed. However, there was a bug in signtool.exe where an attempt to add a second signature did not fail, and instead corrupted the cat file. Validation steps were added in the signing process to avoid this situation, and this broke builds.

* Update Signing.props

Co-authored-by: Larry Ewing <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants