Repository navigation
Replies: 1 comment 1 reply
|
Yes. Every release asset, including the The packages aren't GPG-signed. I've also asked for a sponsor to get Fresh into Debian: https://bugs.debian.org/1151577 |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello Noam,
First of all, thank you for developing and maintaining Fresh.
I'm working on a Debian-based personal project called CLIOS (still unpublished as of this day as it's still under heavy development), which includes additional security controls for downloading, verifying and installing third-party software.
Fresh is one of the applications I'd like to support as it has become a cornerstone of my project, and I've been developing a dedicated updater for its official Debian packages.
During this work, I encountered a question concerning release authenticity.
Although HTTPS and SHA256 checksums provide useful integrity guarantees, they don't independently establish that a release artifact was genuinely authorized by its publisher.
I noticed that Fresh already makes use of GitHub's artifact-attestation mechanisms, but I haven't yet established whether these cover the Debian packages.
May I respectfully ask whether the official
.debartifacts are covered by verifiable attestations? If not, would you consider introducing cryptographic signatures for release packages, perhaps using a dedicated signing key?My intention isn't to suggest that your current distribution process is insecure, but rather to establish a stronger, independently verifiable chain of trust for automated installations at least until Fresh is eventually included in Debian's official repositories.
I fully appreciate that maintaining signing infrastructure introduces additional work, so I would completely understand if this isn't something you wish to pursue.
Thank you for your time and for making Fresh available.
Best regards,
Bruno H. Michele
All reactions