The sha2 stuff causes build failures on a number of architectures. E.g.:
http://buildd.debian.org/fetch.php?pkg=coreutilsver=5.97-1arch=armstamp=1153929302file=logas=raw
http://buildd.debian.org/fetch.php?pkg=coreutilsver=5.97-1arch=alphastamp=1153938804file=logas=raw
Just a reminder for Debian users watching this bug: while waiting for
this to be integrated upstream (should be in forthcoming 6.x release
of coreutils), I maintain Debian packages which are identical to the
Sarge packages except they include the sha2 utilities. The packages
in question, along
On Wed, Jul 26, 2006 at 11:35:55AM +0200, you wrote:
Naturally, I'd very much appreciate it if this patch were added to the
Debian patches...
I'll admit the FUCK debian commentary makes me less interested in
working with you.
FYI, the last dialog about this patch was that there was still
On Wed, Jul 26, 2006 at 07:30:12AM -0400, Michael Stone wrote:
I'll admit the FUCK debian commentary makes me less interested in
working with you.
I'll offer apologies (in private) if you took this personally - it was
not meant as such. But nobody says you have to work with me: the
patch is
David Madore [EMAIL PROTECTED] wrote:
md5 has been broken for some time now; sha1 also has been, more
recently (an actual collision is not known, so far, but a way to
produce one in a reasonable amount of computer time has been
provided). Consequently, the md5sum and sha1sum utilities should
Can I ask you to take a look at the attached patch? It is not yet
satisfactory (at least, it needs to be forwardported to the CVS
version, as I worked against 5.2.1 because I wanted to install this
ASAP on my Debian boxen), but maybe we can start from this to discuss
what needs to be done.
On Sat, Aug 27, 2005 at 04:30:51PM +, Eric Blake wrote:
Would it make more sense to have a single sha utility that takes
an argument of which algorithm to use, defaulting to the most
secure, then the user can define wrappers to invoke a non-default
algorithm? For example, 'sha
David Madore [EMAIL PROTECTED] wrote:
Yes, I am willing to do that.
Great.
I'll send you the copyright forms.
My requesting a `clean' patch means we're pretty picky,
and that the more of the following you can do, the better.
Can I ask you to take a look at the attached patch? It is not yet
Package: coreutils
Version: 5.2.1-2
Severity: wishlist
md5 has been broken for some time now; sha1 also has been, more
recently (an actual collision is not known, so far, but a way to
produce one in a reasonable amount of computer time has been
provided). Consequently, the md5sum and sha1sum
9 matches
Mail list logo
