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

Package Signatures Technical Details #6250

Closed
rido-min opened this issue Dec 4, 2017 · 3 comments
Closed

Package Signatures Technical Details #6250

rido-min opened this issue Dec 4, 2017 · 3 comments

Comments

@rido-min
Copy link

rido-min commented Dec 4, 2017

Status: InReview

This issue should be used to discuss the spec Package Signatures Technical Details

Discussion should happen on this issue. Please link other issues with similar asks to this one

@hach-que
Copy link

Are there any impacts for third-party clients that push to nuget.org? I'm having to do work now because of the breaking change around the X-NuGet-Client-Version: 4.1.0 header, and I want to know if in the future Protobuild will suddenly be unable to push or pull to nuget.org because of package signing.

@rido-min
Copy link
Author

@hach-que package signing is designed to be fully backwards compatible. This means that older clients can pull signed and unsigned packages. There are no new requirements for push, and NuGet.org will accept unsigned packages.

@rrelyea
Copy link
Contributor

rrelyea commented Jan 11, 2018

4.6 work on this specification is done.
We still need some (likely) 4.7 details determined during 4.6, so that we won't blow up with repo signatures in a package with 4.6 client.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants