[Fwd: Re: [Help-gnutls] libgcrypt]

Preeti Shandilya preeti.shandilya at aricent.com
Tue May 27 07:45:19 CEST 2008

Hi Werner  !

Thanks for your response

We could successfully run our product using following version of libraries            libgcrypt-1.2.2

But libgcrypt-1.4.1 gives core.

Attached is config.log :
Following is the system information through prtconf

-----Original Message-----
From: Werner Koch [mailto:wk at gnupg.org]
Sent: Friday, May 23, 2008 11:40 PM
To: Preeti Shandilya
Cc: gcrypt-devel at gnupg.org
Subject: Re: [Fwd: Re: [Help-gnutls] libgcrypt]


There might be an alignment problem.

  #define W (ctx->keySched2)
    for (r = 1; r < ctx->ROUNDS; r++)
        w = W[r][0];
        *((u32*)w) = *((u32*)U1[w[0]]) ^ *((u32*)U2[w[1]])
          ^ *((u32*)U3[w[2]]) ^ *((u32*)U4[w[3]]);

W is

      byte keyschedule[MAXROUNDS+1][4][4];
    } u2;
  } RIJNDAEL_context;

  #define keySched  u1.keyschedule
  #define keySched2 u2.keyschedule

Thus it should be properly aligned.  Well, on a 32 bit boundary for
array elements > 0.  Ux is might not be properly aligned, hwoever all
compilers I know place tables on a word boundary and thus there should
be no problem.

We never had any problems with that code, it is really old and thus can
be believied to be matured.  It is used in gpg as well.  Thus I wonder
what is special on your setup.

What we need are hardware information and the config.log from the
libgcrypt build as well as a log of the make run.



Die Gedanken sind frei.  Auschnahme regelt ein Bundeschgesetz.

"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility forloss or damage arising from the use of the information transmitted by this email including damage from virus."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.log
Type: application/octet-stream
Size: 63320 bytes
Desc: config.log
URL: </pipermail/attachments/20080527/4c177bbe/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: info
Type: application/octet-stream
Size: 2583 bytes
Desc: info
URL: </pipermail/attachments/20080527/4c177bbe/attachment-0003.obj>

More information about the Gcrypt-devel mailing list