** Changed in: smart
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/522513
Title:
SHA256 checksum for apt-deb
--
ubuntu-bugs mailing list
Now (r991), it will check MD5 first and then SHA too (prefer SHA256,
when available)
** Changed in: smart
Milestone: None = 1.4
** Changed in: smart
Status: New = Fix Committed
** Changed in: smart (Ubuntu)
Status: Fix Released = New
--
SHA256 checksum for apt-deb
Upon inspection, the linked branch has been merged and this code is
included in v1.3.
** Changed in: smart (Ubuntu)
Status: New = Fix Released
** Changed in: smart (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: smart
Status: New = Fix Released
--
SHA256 checksum
Well, the sha256 parser has been merged but the code only checks md5 if
present (if so, sha256 is skipped)
The question is whether it should change to checking sha256 first,
otherwise sha1 and lastly fall back to md5.
This was suggested for 1.2, but postponed for performance reasons (I think
The main reason this only affects apt-deb and not yum-rpm is because the
repodata deletes the older checksums, while the debian repository has
all three checksums present. Otherwise the same code is shared between
all backends.
--
SHA256 checksum for apt-deb
** Also affects: smart (Ubuntu)
Importance: Undecided
Status: New
--
SHA256 checksum for apt-deb
https://bugs.launchpad.net/bugs/522513
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
