-
Notifications
You must be signed in to change notification settings - Fork 7
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
How to add a binary target file with offline keys #222
Comments
Another thing I've noticed is a more serious bug: When you add a target file through this API, all custom data not known by ota-tuf will be lost for all targets. I have a field |
wrt to the 1st question, you'd have to use garage-sign to add that binary target. The server will not accept binary packages directly if the keys are offline, as it cannot sign the resulting metadata. About the 2nd question, which version of tuf-repo are you using? This case is handled explicitly ( Line 97 in dd3fab7
|
I just discovered I'm running an out-of-tree version based on this PR: However, that PR include the commit you just referenced. Here's a simplified list of steps I can do to reproduce the issue:
I can the run something like the following:
which shows that all the targets with "docker_apps" in the custom data get lost. |
What is app.txt and ota-dockerapp.py ? Which apis are they calling? |
In any case, I just managed to reproduce this. We will create a ticket to fix this. |
Not deployed to production, yet, but will be soon. |
I've been able to add binary target files to the repo server via the API(eg PUT api/v1/user_repo/targets/) and Web UI when I have online keys. However, my production instance uses offline keys. I'm not quite sure how to upload a file to the reposerver and have it added to my targets.json properly?
The text was updated successfully, but these errors were encountered: