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

Image replication doesn't carry the signature in Notary. #2102

Closed
reasonerjt opened this issue Apr 21, 2017 · 4 comments
Closed

Image replication doesn't carry the signature in Notary. #2102

reasonerjt opened this issue Apr 21, 2017 · 4 comments

Comments

@reasonerjt
Copy link
Contributor

When an image is replicated from a Harbor instance deployed with notary to another Harbor instance, if the image is signed, the signature information in notary will not be replicated.

Due to some fundamental design of notary when the hostname of registry is changed the image has to be re-signed, but it can't be done at server-side because the keys are stored offline. Docker is working to solve this issue. So this is a limitation.

@stuclem
Copy link
Contributor

stuclem commented May 2, 2017

@reasonerjt I only just saw this. Belatedly added the issue to the release notes. Removing kind/note tag.

@stuclem stuclem removed the kind/note label May 2, 2017
@stale
Copy link

stale bot commented Oct 7, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale label Oct 7, 2018
@stale stale bot removed the Stale label Oct 10, 2018
@saarktim
Copy link

Does this issue still affect to the latest version of Notary?

@xaleeks
Copy link
Contributor

xaleeks commented Nov 19, 2020

dupe of #8303

@xaleeks xaleeks closed this as completed Nov 19, 2020
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