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

Please gpg sign release #2878

Closed
jonathancross opened this issue Oct 17, 2024 · 2 comments
Closed

Please gpg sign release #2878

jonathancross opened this issue Oct 17, 2024 · 2 comments
Labels
need/triage Needs initial labeling and prioritization

Comments

@jonathancross
Copy link

I didn't see signature files with the latest downloads meaning that users are just trusting github.
Would be much better if devs signed binaries (and release tags) so users could have more confidence in the builds.

@jonathancross jonathancross added the need/triage Needs initial labeling and prioritization label Oct 17, 2024
Copy link

welcome bot commented Oct 17, 2024

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We are triaging issues on weekly basis and aim to give initial feedback within a few business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.tech if you just need general support.

@lidel
Copy link
Member

lidel commented Oct 17, 2024

Marking as duplicate of #2867

Please see my note how current artifacts are built (fully on github CI, so you have to trust github anyway) and post your threat model, and ideas on what should be improved and why on that issue 🙏

@lidel lidel closed this as not planned Won't fix, can't repro, duplicate, stale Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/triage Needs initial labeling and prioritization
Projects
No open projects
Status: No status
Development

No branches or pull requests

2 participants