Share your knowledge at the LQ Wiki.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 06-23-2009, 02:18 PM   #1
LQ Newbie
Registered: Jun 2009
Posts: 2

Rep: Reputation: 0
md5 values convention should be for uncompressed version of the file

Are md5 values published next to the compressed version of the file assumed to be for the uncompressed version?

There should be an obligatory "uncompressed md5:"
instead of what I usually see: "md5".
That would help me, as a newbie.

I know, I know, it can't be the compressed version's md5,
for the filename does not indicate the level of compression.
But I'm not sure about the convention, and I'd like some clarity.

Thanks in advance.
Old 06-23-2009, 02:36 PM   #2
Registered: Dec 2007
Location: Charleston WV, USA
Distribution: Slackware 12.2, Arch Linux Amd64
Posts: 896

Rep: Reputation: 69
Originally Posted by cpiral View Post
Are md5 values published next to the compressed version of the file assumed to be for the uncompressed version?
In general, no. The whole point of publishing md5 sums is for the user to immediately check the integrity of the download before doing anything with the file. But different places can have different opinions on that.
Old 06-24-2009, 01:12 PM   #3
LQ Newbie
Registered: Jun 2009
Posts: 2

Original Poster
Rep: Reputation: 0
two md5 per app download?

Assuming an md5 to check the file as soon as it's downloaded, then
one would need yet another md5 to check the application itself after
it has been uncompressed.

Practically all application packages are compressed before downloading--
even binaries--and there are many types and levels of compression.
Each method would result in a different md5.

An app has two distributors. The first distributor is the person
who packages the code and it's libraries into a release version.
THere is a lot of decision making and resulting accountability.
The second distributor is the person who gets a release from
its origin and then acts as a downloading center for apps. Or
the second distributor may be one who creates binaries of the app.

We need a general, publishable md5 for the release itself.
Each release or version needs an md5 I'm calling the "general md5".
The release manager should attach this md5 in the README file,
and publish the release md5 for all to verify the particular release
is the one originally packaged and released.

If there is an md5 for the compressed package only,
and not a general md5 for the release itself, then
then secondary distributors hide any corruption to the original package.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Solaris 5/08 MD5 Checksum Values UMG:Chicken_Sop Solaris / OpenSolaris 5 05-23-2011 08:05 AM
uncompressed file size without uncompress? Lander Programming 3 06-13-2006 04:21 AM
file naming convention soldan Linux - Newbie 13 05-15-2006 11:11 AM
MD5 values for mandrake 10 wogga Linux - Software 5 06-01-2004 02:26 AM
Audio - uncompressed file format Beuzekom Linux - Software 3 02-10-2004 08:53 AM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 02:46 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration