Fully match the upstream codesign requirements
See original GitHub issueDescription
In Chromium 98.0.4758.109, there was a commit which changed signature verification for PWAs
https://chromium.googlesource.com/chromium/src/+/e660f5610cf324520b9db9ce86259424df1f15fb
We got this passing with https://github.com/brave/brave-core/pull/12418 - but ~part of codesign_requirements_basic is commented out:~ we are missing and certificate leaf[subject.OU] = KL8N8XSYF4 at the end
return 'and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists / and certificate leaf[field.1.2.840.113635.100.6.1.13] / exists */'
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
TN3127: Inside Code Signing: Requirements - Apple Developer
When you sign code with Xcode or codesign , they apply a default designated requirement (DR) based on the code signing identity you...
Read more >Check upstream tarball signatures - packaging-committee
#610 Packaging guidelines: Check upstream tarball signatures ... Of course, you should check the fingerprint of the resulting key matches what you expect, ......
Read more >Kernel Module Packages Manual - SUSE Documentation
This document specifies the requirements for RPM packages that contain ... of the same kernel package on different architectures will not match either....
Read more >Participation and Co-creation in Citizen Science | SpringerLink
... these debates are grouped under the terms upstream engagement ... in the context of health-related and environmental science, fully ...
Read more >Sonarr - Dive in
Notifications and fully customizable quality profiles. ... It is possible to install Sonarr manually from upstream using the .tar.gz download.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@diracdeltas @bsclifton this ticket is not correct. We are missing
and certificate leaf[subject.OU] = KL8N8XSYF4at the end.any update here?