nextcloud / nextcloud/desktop

Checksum for published packages

Open
#8,959 3 comments 0 reactions 1 assignee Claimed by @mgallien View on GitHub
Dominant language
C++
Stars
3.9k
Forks
1k
Avg merge
1d 17h
Merged PRs (30d)
123

Description

### How to use GitHub

* Please use the 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to show that you are interested into the same feature.
* Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
* Subscribe to receive notifications on status change and new comments.

---

## Feature request

**Which Nextcloud Version are you currently using:** (see administration page)
4.0.0

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

When building a package for a distro and upon receiving a contribution it is quite important to know the tarball is authentic. A checksum posted together with the tarball would be most helpful.

**Describe the solution you'd like**
A clear and concise description of what you want to happen.
B
a checksum file together with each published package to verify authenticity., e.g. sha256sum

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.