Opened 16 years ago

Closed 15 years ago

Last modified 7 years ago

#2449 closed enhancement (wontfix)

Change book to use sha1sum

Reported by: DJ Lucas Owned by: DJ Lucas
Priority: low Milestone: x-future
Component: BOOK Version: SVN
Severity: minor Keywords:


I've noticed that a few sites are no longer providing an md5sums file and only sha1sums. Open discussion on blfs-dev about this after 6.3 is out the door.

Change History (6)

comment:1 by DJ Lucas, 16 years ago

Status: newassigned

comment:2 by bdubbs@…, 16 years ago

Priority: normallow

I'm going to change this to low priority. It's not really critical because an editor can produce a missing md5 sum after manually checking the the sha1 sum. There are a lot of things that would be a better use of an editor's time than this.

I wouldn't be opposed to just adding an sha1 sum line to each package as it is updated. My scripts that generate the stats for packages can be trivially updated to add an sha1 sum and pasting that in for a new package would be be OK. The only issue would be that some packages would have both and some only an md5 sum.

Although the sha1 sum is technically better, the difficulty of producing a modified package with the same md5 sum as the original and still be able to build a package is still pretty difficult.

comment:3 by DJ Lucas, 16 years ago

Oh, I agree about priority, much better things to do. :-) This is not a problem by any means, if you know a way to forge sums, I'd like to know exactly how! It's just something I've noticed as I'm looking for updated packages. Figured I'd make mention of it after we get 6.3 out the door. I like better the idea of maybe adding it.

comment:4 by Randy McMurchy, 16 years ago

Milestone: 7.0future

comment:5 by DJ Lucas, 15 years ago

Resolution: wontfix
Status: assignedclosed

Closing WontFix to get it out of the queue. We can revisit later if needs be.

comment:6 by bdubbs@…, 7 years ago

Milestone: futurex-future

Milestone renamed

Note: See TracTickets for help on using tickets.