From gokaysa@gmail.com Tue Oct 28 08:30:41 2008 Date: Tue, 28 Oct 2008 17:30:41 +0200 From: Gokay Saldamli To: Cody Walker Cc: Cetin Kaya Koc Subject: Re: s-hash documentation X-IMAPbase: 1279770017 1 Status: O X-Status: X-Keywords: X-UID: 1   check this out.   a note: in non-linear system transform high and low bits of p_prism i.e. p_prism_H and p_prism_L respectively were placed wronglyin the first maple version. it was (sprime_prism, p_prism_H) and corrected with (sprime_prism, p_prism_L) similarly (s_prism_{p_prime}, p_prism_L) is corrected with (s_prism_{p_prime}, p_prism_H) good luck gokay   On Tue, Oct 28, 2008 at 4:17 PM, Gokay Saldamli wrote:   you have a point, it seems the padding is implemented wrongly in maple. please have a look at the following link http://www.itl.nist.gov/fipspubs/fip180-1.htm especially the example in section 4. I will use that example, correct it and resend it. thanks... gokay On Tue, Oct 28, 2008 at 3:39 PM, Cody Walker wrote: Hi,  I looked at the maple code and ran some tests. The output doesn't match that of our code, but I think I have found one of the reasons. Your program seems to add an incorrect length in the padding process (at least in the short test messages I tried). I tried to look into the issue, but I can't find where this happens in the code. Can you try to fix the issue (or explain why this behavior is correct).  Thanks, Cody On Oct 28, 2008, at 2:49 AM, "Gokay Saldamli" wrote:   Dear Megan, First let me see what you have done so far.  today and tomorrow I will be out off office and will be working on these issues. gokay    PS. At last I finished the the working maple 8 code for whole shash including the hash generation for different hash sizes.   ---------- Forwarded message ---------- From: Megan L. Maguire Date: Tue, Oct 28, 2008 at 7:09 AM Subject: s-hash documentation To: Gokay Saldamli Cc: koc So the deadline for submission is rapidly approaching, and we are desperately trying to finish the required documentation. However the design rationale and security analysis sections are giving us trouble, mainly because we simply don't know a lot about why s-hash is secure or what you took into consideration when designing it. Also, we need more explicit information on the advantages and disadvantages of s-hash, and it's ability to be implemented on platforms with limited resources, etc. Basically, we have the math background and algorithm description sections done, but we need help with everything else. -- Megan L. Maguire mmaguire@umail.ucsb.edu *panic* *hyperventilate* *panic* *hyperventilate* *panic* *hyperventilate* *panic* *hyperventilate* *panic* *hyperventilate* *panic* *hyperventilate* [ Part 2, Application/OCTET-STREAM (Name: "shash_v2.mws") 124KB. ] [ Unable to print this part. ]