this post was submitted on 15 Oct 2023
6 points (57.1% liked)
Linux
48224 readers
978 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Signature = authentication: signed (presumably) by the private key of the project owner(s).
Checksum = integrity: confirms the file hasn't been corrupted or tampered with in transit.
If the checksum file is signed by the project owners, that's the highest guarantee available that the file on your local is identical to the one compiled by the project owner(s).
Where do you get the public key to verify the signature from? My point being, that you have to trust someone. I don't really see the benefit of trusting a key server, that the public key really belongs to the owner over a checksum file being published on the website of the owner.
You mean trusting a key published on a different site (and replicated between all GPG key registries), Vs a checksum published on the same website that's serving you the suspect ISO?
Which do you think is more likely to also be compromised?
Oh you are absolutely right about it being much harder to compromise the distro website as well as a key server. And as much as I am aware of the concept of the web of trust, I still do not get how you securely draw a relation between a key on a third party website and the publisher of a distro?
I just checked for OpenSuse and Fedora. Both link to their keys on their own website, which both target files on their own domain. And even if they linked to a third party, what is stopping an attacker, who already managed to swap the iso and checksum file to also change the link to the key server?
You are right about already imported keys. But why would someone, who does not already have distro xyz installed, have the keys of the publisher of distro xyz imported?
Thanks in advance for the discussion!
You publish the master GPG key in a DNS record for the website you download from, and you sign the DNS records with DNSSEC. (Yes I know, ironically the TLS cert for the page with the explanation has expired last month...) You can also use DNS records to enable autodiscovery of the GPG keyserver hosting the relevant master key.
Once you have one GPG key you can trust you can use it to verify downloads as well as other GPG keys.
Unfortunately most Linux distros don't use DNS records. Most of them publish the GPG key on the same page as the checksum, which can be compromised just the same, you are correct. Some of them publish their key on a separate keyserver, but to find that key you need to know its fingerprint or its associated email address... and if those are provided via the download page then you're back to square one. 😆
TIL about GPG keys in DNS records. Thanks, that is indeed a real benefit!
Thank you. I think the issue here is most people (unlike you) have no clue what I'm talking about, which explains the immaturity in the comments section.