Bug#460422: Alignment issue with sha1 code from gnulib

2008-01-31 Thread Simon Josefsson
Jim Meyering <[EMAIL PROTECTED]> writes: > Bruno Haible <[EMAIL PROTECTED]> wrote: > >> Jim Meyering wrote: >>> Thanks for the suggestion. It looks like a good one. >> >> The suggestion also applies to the 'md5' module, after which the 'sha1' >> module >> is modeled. > > Yep. md2 and md4 too. >

Bug#460422: Alignment issue with sha1 code from gnulib

2008-01-31 Thread Simon Josefsson
Jim Meyering <[EMAIL PROTECTED]> writes: > Bruno Haible <[EMAIL PROTECTED]> wrote: > >> Jim Meyering wrote: >>> Thanks for the suggestion. It looks like a good one. >> >> The suggestion also applies to the 'md5' module, after which the 'sha1' >> module >> is modeled. > > Yep. md2 and md4 too. >

Bug#460422: Alignment issue with sha1 code from gnulib

2008-01-31 Thread Jim Meyering
Jim Meyering <[EMAIL PROTECTED]> wrote: > David Shaw <[EMAIL PROTECTED]> wrote: >> Peter Palfrader reported a bug against the sha1 code in paperkey, but >> that code actually comes from gnulib, so I'm referring it to you. >> >> The issue comes up (as noted in the comment) if resbuf is not 32-bit >>

Bug#460422: Alignment issue with sha1 code from gnulib

2008-01-31 Thread Jim Meyering
Bruno Haible <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote: >> Thanks for the suggestion. It looks like a good one. > > The suggestion also applies to the 'md5' module, after which the 'sha1' module > is modeled. Yep. md2 and md4 too. For now, I've pushed the sha1 changes. > But if you apply

Bug#460422: Alignment issue with sha1 code from gnulib

2008-01-31 Thread Bruno Haible
Jim Meyering wrote: > Thanks for the suggestion. It looks like a good one. The suggestion also applies to the 'md5' module, after which the 'sha1' module is modeled. But if you apply the suggestion to both the sha1 and md5 modules, we get an additional difference to glibc code. OTOH, Simon hims

Bug#460422: Alignment issue with sha1 code from gnulib

2008-01-31 Thread Simon Josefsson
Bruno Haible <[EMAIL PROTECTED]> writes: > Jim Meyering wrote: >> Thanks for the suggestion. It looks like a good one. > > The suggestion also applies to the 'md5' module, after which the 'sha1' module > is modeled. > > But if you apply the suggestion to both the sha1 and md5 modules, we get > an

Bug#460422: Alignment issue with sha1 code from gnulib

2008-01-30 Thread Jim Meyering
Jim Meyering <[EMAIL PROTECTED]> wrote: ... > Thanks for the suggestion. It looks like a good one. > However, I don't want to change the type of the resbuf parameter. > Here's the change I'm considering: And of course, coreutils/lib/sha*.c would get the same change. -- To UNSUBSCRIBE, email

Bug#460422: Alignment issue with sha1 code from gnulib

2008-01-30 Thread Jim Meyering
David Shaw <[EMAIL PROTECTED]> wrote: > Peter Palfrader reported a bug against the sha1 code in paperkey, but > that code actually comes from gnulib, so I'm referring it to you. > > The issue comes up (as noted in the comment) if resbuf is not 32-bit > aligned. Rather than requiring all programs t

Bug#460422: Alignment issue with sha1 code from gnulib

2008-01-29 Thread David Shaw
Hello, Peter Palfrader reported a bug against the sha1 code in paperkey, but that code actually comes from gnulib, so I'm referring it to you. The issue comes up (as noted in the comment) if resbuf is not 32-bit aligned. Rather than requiring all programs that use the gnulib sha1 code to align t