-
Notifications
You must be signed in to change notification settings - Fork 134
Ensure no signed files skip verification #4929
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
Comments
Are all file types covered now @ellahathaway? |
@mmitche There are ~145 extensions that are getting skipped by all OSes. I picked out a few that I think need to be addressed:
Here are the other extensions that are currently getting skipped:
|
Follow-up: 7z, 7zip, bz2, and bzip2 can just be skipped, because they only apply to empty files (empty.7z, empty.7zip, empty.bz2 and empty.bzip2). I think the other file extensions, besides jar, don't have to be signed so they're okay to be skipped. For jar, I can enable jar verification in SignCheck via /p:EnableJarSigningCheck=true. Before I enable jar verification, a fix will need to go into SignCheck because it currently fails when verifying jar files: |
Closing this issue per the comment above. I'm tracking the jar verification work with #4999 |
Not all files that can be validated on .NET Core can be validated on .NET Framework, and vise-versa. See https://github.com/dotnet/arcade/blob/e52018af7f5bab97b0721382d52badfc7edb54f6/src/SignCheck/Microsoft.SignCheck/Verification/SignatureVerificationManager.cs#L91-L117 for the full list.
Due to these differences, we should verify that no signed files skip verification between the Mac, Linux, and Windows verification legs. This work will be more of a sanity check and does not need to go into prod.
The text was updated successfully, but these errors were encountered: