Differences between revisions 1 and 2
Revision 1 as of 2010-03-08 15:08:47
Size: 913
Editor: FranklinPiat
Comment: Initial page
Revision 2 as of 2010-03-08 15:14:43
Size: 1289
Editor: FranklinPiat
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
Line 8: Line 9:
== Rational ==
 * MD5SUMS is considered weak nowadays
 * The checksum has proven to be useful in the past (both for checking the integrity of installed files, to reduce the amount of data to backup, and for security reasons)
 * Some users still want to rely on the checksum provided in the archive to validate the authenticity of files.
Line 9: Line 14:
== policy == == Todo List ==
=== P
olicy ===
Line 12: Line 18:
== Lintian == === Lintian ===
Line 16: Line 22:
== build systems ==
=== debhelper ===
=== Build systems ===
==== debhelper ====
Line 20: Line 26:
=== cdbs === ==== cdbs ====
Line 23: Line 29:
== checksum validation ==
=== debsums ===
=== checksum validation ===
==== debsums ====
Line 27: Line 33:
=== offline checking === ==== offline checking ====

This page tracks the progress in supporting debian/sha256sums in debian packages.

Rational

  • MD5SUMS is considered weak nowadays
  • The checksum has proven to be useful in the past (both for checking the integrity of installed files, to reduce the amount of data to backup, and for security reasons)
  • Some users still want to rely on the checksum provided in the archive to validate the authenticity of files.

Todo List

Policy

  • After squeeze release, replace "should provide md5sums" with "can provide md5sums" and "should provide sha256sums"

Lintian

  • TODO

  • Same as policy

Build systems

debhelper

  • TODO

cdbs

  • TODO

checksum validation

debsums

  • TODO

offline checking

  • Write a tool to validate the checksums offline (i.e when the root partition is mounted as a slave)