Exploding Dragon
Exploding Dragon
> You could also sign existing packages Signing existing packages is not well suited to be done on update, the best option is to create a manual task, sorry I'm...
> Maybe use either https://github.com/ProtonMail/go-crypto or https://github.com/ProtonMail/gopenpgp? It may not work well because the old way of signing is missing. Note: - https://github.com/goreleaser/nfpm/pull/680 - https://github.com/sassoftware/go-rpmutils/pull/21#issuecomment-1100266607
As of now, the pr functionality is complete and only lacks testing.
This PR is ready for review.
Any new update on this @JakobDev ?
Perhaps there is no need to modify the backend code; we can simply use JavaScript for asynchronous uploads on the frontend.
TODO: - [x] Package signatures should be managed by Gitea, custom signatures will result in inconsistencies with index signatures. - [x] Signatures should not be saved under properties - [x]...
> When #25396 was closed some weeks ago, I adopted the PR and rewrote it to look similar to how the other package registries work. I will push my changes...
> When #25396 was closed some weeks ago, I adopted the PR and rewrote it to look similar to how the other package registries work. I will push my changes...
> Thanks again @ExplodingDragon for your work on getting these additional package PRs in. I'm going through the backlog of PRs now, and would love to get to this one....