Repository navigation
chore: pin common, sync, shim for malware seed - #1489
Merged
Merged
Conversation
Live feed still wins. User-space malware.db needs a verified head.cose. Certified installer seed is in the certified pin. Signed-off-by: Corey Butler <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
commonto 15b2ef3d (feat(malwaredb): verify feed head and persist pair common#21).syncto 0e5dfd99 (nvm-windows/sync#18).shimto 65bae811 (feat(proxy): trust malware.db via COSE pair shim#19).Why
User-space
malware.dbis trusted only with a verifiedhead.cose. Live feed still wins. Certified MSI seed is the certified pin, not this one.Testing
Risk
Low. Pins only. Community still has no bundled Program Files seed. Unsigned data-root db is ignored.