Date: Sat, 4 Aug 2012 02:58:42 -0500 From: "jfoug" <jfoug@....net> To: <john-dev@...ts.openwall.com> Subject: RE: SHA-384 support in Jim's SHA2 code NOTE, the extern .C function names will probably change. I am thinking: JtR_sha512_init, JtR_sha512_update, ... etc. The #defines (which are what should be used), will stay the same, so it will simply be a recompile change. I know for SURE that the names are compatible with oSSL, but not fully sure they work with other SHA libs (like CryptoLib). By adding JtR_* to the functions (and possibly the data), there should NEVER be a chance of collision. NOTE, we probably should prepend a JtR wort on the front of our gost code, since gost is in newer oSSL's. Jim. >From: Dhiru Kholia [mailto:dhiru.kholia@...il.com] > >On Sat, Aug 4, 2012 at 12:54 PM, jfoug <jfoug@....net> wrote: >> From sha2.h >> >> #define SHA512_CTX sha512_ctx >> #define SHA384_Init(a) sha512_init(a,0) >> #define SHA512_Init(a) sha512_init(a,1) >> #define SHA512_Update(a,b,c) sha512_update(a,b,c) #define >> SHA384_Update(a,b,c) sha512_update(a,b,c) >> #define SHA512_Final(a,b) sha512_final(a,b) >> #define SHA384_Final(a,b) sha512_final(a,b) > >How did I miss them? Thanks Jim and sorry for the trouble!
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.