How to make use of MD5SUMS.sign file on Debian ISO downloads
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
How to make use of MD5SUMS.sign file on Debian ISO downloads
Hi,
I know how to use the MD5SUMS file to verify the integrity of ISO download. However I am not sure how to use the MD5SUMS.sign files that accompanies the MD5SUMS file.
Md5sum hash files contains an byte-a-byte generated number, where you can check if at least 1 byte is changed. Useful to detect download errors or any modification on the original file.. if the numbers match file is identical.
md5.sign you are referred, is also a check for the digital sign of the publisher, wich is an file too and is important that it is unchanged.
You use this when installing stuffs from many package managers, also you can use "gpg --verify", here a little fromman page:
Quote:
--verify
Assume that the first argument is a signed file or a detached signature and verify it without generating any
output. With no arguments, the signature packet is read from stdin. If only a sigfile is given, it may be a
complete signature or a detached signature, in which case the signed stuff is expected in a file without the
".sig" or ".asc" extension. With more than 1 argument, the first should be a detached signature and the
remaining files are the signed stuff. To read the signed stuff from stdin, use '-'’ as the second filename.
For security reasons a detached signature cannot read the signed material from stdin without denoting it in
the above way.
You use this when installing stuffs from many package managers, also you can use "gpg --verify", here a little fromman page:
Hope it helps
Ok here is what I did:
Code:
debian:/mnt/temp# gpg --verify MD5SUMS.sign
gpg: Signature made Sat 14 Feb 2009 11:51:23 PM PST using DSA key ID 88C7C1F7
gpg: Can't check signature: public key not found
debian:/mnt/temp#
Not sure what is happening here. I understand that the sign file MD5SUMS.sign file exits so that we can verify that the file MD5SUM was being generated by the person who actually did generate it. Not sure what step am I missing?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.