Skip to content

[Collections] Check for collections that are required to be signed #3297

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

Merged
merged 2 commits into from
Feb 23, 2021

Conversation

yim-lee
Copy link
Contributor

@yim-lee yim-lee commented Feb 20, 2021

Motivation:
If a collection source has an entry in the certificate pinning configuration that it must be signed. Currently we are not checking for this.

Modifications:
Update JSONPackageCollectionProvider to check that if a collection is unsigned, then it shouldn't have an entry in the certificate pinning configuration. Otherwise, throw missingSignature error which cannot be bypassed.

@yim-lee
Copy link
Contributor Author

yim-lee commented Feb 20, 2021

@swift-ci please smoke test

@tomerd tomerd added the ready Author believes the PR is ready to be merged & any feedback has been addressed label Feb 21, 2021
Motivation:
If a collection source has an entry in the certificate pinning configuration that it must be signed. Currently we are not checking for this.

Modifications:
Update `JSONPackageCollectionProvider` to check that if a collection is unsigned, then it shouldn't have an entry in the certificate pinning configuration. Otherwise, throw `missingSignature` error which cannot be bypassed.
@yim-lee
Copy link
Contributor Author

yim-lee commented Feb 23, 2021

@swift-ci please smoke test

@yim-lee yim-lee merged commit 8e919a0 into swiftlang:main Feb 23, 2021
@yim-lee yim-lee deleted the signing-required branch February 23, 2021 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready Author believes the PR is ready to be merged & any feedback has been addressed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants