Lines Matching refs:to
5 While this is my "release" version, due to lack of additional
6 official test vectors against which to verify this implementation's
26 The interface is similar to the interface to SHA-1 found in the OpenSSL
40 data is handled. The NIST document describes how to handle sub-byte
49 implementation designed to use only 32-bit words (emulating the
57 however, that suggest ways to speed things up without breaking
58 portability. I also welcome suggestions to improve portability.
91 included in the inttypes.h header file. Those wanting to use inttypes.h
92 need to define this either in sha.h or at compile time.
95 to edit both sha2.h and sha2.c and define things by hand in the appropriate
100 compile to either equal LITTLE_ENDIAN or BIG_ENDIAN. If your system
101 does not define these, you may need to define them by hand in the sha.c
102 file according to the byte ordering conventions of your system.
107 code will default to memset()/memcpy(). You can define either at the
112 the code will use macros to partially "unroll" the SHA transform
115 to optimize things. For example, on the FreeBSD and Linux x86 systems
125 The code in sha2.c and sha2.h is intended to be portable. It may
133 To get sha2.c/sha2.h working under Windows, I had to define
134 SHA2_USE_INTTYPES_H, BYTE_ORDER, LITTLE_ENDIAN, and had to comment
136 I got the test program to run and verified that all the test
142 If you make changes to get it working on other architectures, if you fix
144 efficiency that would be relatively portable and you're willing to release
145 your changes under the same license, please send them to me for possible
154 0.8 to 0.9 - Fixed spelling errors, changed to u_intXX_t type usage,
155 removed names from prototypes, added prototypes to sha2.c,
158 0.9 to 0.9.5 - Add a new define in sha2.c that permits one to compile
159 it to either use memcpy()/memset() or bcopy()/bzero()
162 compile with SHA2_UNROLL_TRANSFORM to enable. It takes
163 longer to compile, but I hope it is a bit faster. I
164 need to do some test to see whether or not it is. Oh,
165 in sha2.c, you either need to define SHA2_USE_BZERO_BCOPY
166 or SHA2_USE_MEMSET_MEMCPY to choose which way you want
167 to compile. *Whew* It's amazing how quickly something
168 simple starts to grow more complex even in the span of
169 just a few hours. I didn't really intend to do this much.
170 0.9.5 to 0.9.6 - Added a test program (sha2test) which tests against several
174 0.9.6 to 0.9.7 - Fixed a bug that could cause invalid output in certain
176 data is hashed. Also changed the rotation macros to use
184 as well as made a few other minor changes to get rid of
186 0.9.7 to 0.9.8 - The bug fix in 0.9.7 was incomplete and in some cases made
189 because of the lack of test vectors against which to do such
193 0.9.8 to 0.9.9 - Fixed some really bad typos and mistakes on my part that
195 access for testing before this version. Thanks to
196 Lucas Marshall for giving me access to his OS X system.
197 0.9.9 to 1.0.0b1 Added a few more test samples and made a few changes to
207 1.0.0b1 to 1.0 RELEASE Fixed an off-by-one implementation bug that affected
211 hashed data lengths L = 111 + 128 * X. Thanks to Rogier
215 easier to manage. The sha2prog.c file was rewritten to
216 be more useful to me, and I got rid of the old C testing
235 Please don't send support questions. I don't have the time to answer and
240 letting me know who you are and what use to which it is being put. There
241 is no requirement to do so. I just think it would be fun.