On Wed, 9 May 2007, Johannes Schindelin wrote: > > To be honest, I wouldn't even be *thinking* about the endianity of SHA-1 > > octet representation (you don't usually really deal with the hash as > > with a number, so expecting to have it in native endianity is not very > > natural; you just deal with it as with a data blob) and the > > "(big-endian)" would only confuse me and get me thinking about "huh, do > > they swap the bytes, or wait, they don't, ...?!". > > > > But that's maybe just me. > > But then, maybe it is just me? I got it completely wrong the first time, > fully expecting the calculations to be carried out in host endianness for > performance reasons. I think the Mozilla implementation carries out calculations in host endianness, and transfers data from the input to the internal state and from the internal state to the final hash with shifts and masks. Which calculations are you seeing that involve byte order? -Daniel *This .sig left intentionally blank* - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
