Bug 477029

Summary: Support sha256sums for file checksumming
Product: [Fedora] Fedora Reporter: James Bowes <jbowes>
Component: createrepoAssignee: Luke Macken <lmacken>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: bkearney, james.antill, kwirth, lmacken, mitr, pfrields
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-26 16:36:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 461972, 477030, 480791    

Description James Bowes 2008-12-18 18:58:41 UTC
We should support sha256 for checksums on both repodata files, and on the rpms themselves.

Comment 1 James Antill 2008-12-18 20:00:43 UTC
createrepo doesn't store the file checksums, so nothing needs to change here.

Comment 2 Miloslav Trmač 2009-01-20 15:57:10 UTC
repomd.xml can refer to other files using SHA-256 using the (deprecated) -s flag, but the package checksums (<package><checksum type="sha" pkgid="YES">..., <package pkgid="...">) are hard-coded to use SHA-1.

Because these checksums are used to verify authenticity of downloaded packages, they should be using SHA-256 as well.

The SHA-1 package checksums are hard-coded in yum.packages and createrepo.yumBased.

In addition, modifyrepo is hard-coded to use SHA-1 for added repodata files.

Comment 3 seth vidal 2009-01-26 16:36:42 UTC
This is now fixed in upstream createrepo:
http://createrepo.baseurl.org/gitweb?p=createrepo.git;a=commitdiff;h=3b43f1280d94776689816cf96c6cc8135726b240