I'm not so sure about that. And if we ever need to implement the original "SHA" function, what should that be named? (Google yields 209 000 hits for "sha1 hash", and only 84 500 for "sha hash", using "all of the words"-queries).
Well, then I'll rename it SHA1.
Odd. No idea what it collided with?
object(is 12), whatever that is.
But on second thought, feed/drain might need an arbitrary large buffer.
That is of course easy to add in a Pike wrapper with String.Buffer.
There are also a few different conventions for padding, so I hope the class can be extended easily.
Well, no. Even if you inherit it you can not access the backlog. We could either add accessor methods or add some sort of static pike variables. But we don't HAVE to do that now...
/ Martin Nilsson (saturator)
Previous text:
2004-02-04 21:47: Subject: Crypto naming
SHA is the name most people would guess. The documentation says it is SHA1.
I'm not so sure about that. And if we ever need to implement the original "SHA" function, what should that be named? (Google yields 209 000 hits for "sha1 hash", and only 84 500 for "sha hash", using "all of the words"-queries).
Yes, I tried Nettle.Buffer first, but it doesn't work (some sort of name collision I think).
Odd. No idea what it collided with?
Perhaps it should be renamed, and perhaps it would make sense with a feed/drain interface.
But on second thought, feed/drain might need an arbitrary large buffer. The current convention (if I understand it correctly) never needs to save more than one block of data. Which is nice from an implementation point of few, in particular as the implementation is written in C.
There are also a few different conventions for padding, so I hope the class can be extended easily.
/ Niels Möller (vässar rödpennan)