Mailing List Archive

[Fwd: Re: [Help-gnutls] libgcrypt]
Re: [Fwd: Re: [Help-gnutls] libgcrypt] [ In reply to ]
Hi,

That forwarded bug message is not very helpful. Too many things are
mixed up or cut off. The orginal reporter (who's email is not given)
should prepare a proper bug report and send it again.


Salam-Shalom,

Werner


--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.


_______________________________________________
Gcrypt-devel mailing list
Gcrypt-devel@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gcrypt-devel
Re: [Fwd: Re: [Help-gnutls] libgcrypt] [ In reply to ]
Hi,

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

union
{
PROPERLY_ALIGNED_TYPE dummy;
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.


Salam-Shalom,

Werner

--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.


_______________________________________________
Gcrypt-devel mailing list
Gcrypt-devel@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gcrypt-devel
RE: [Fwd: Re: [Help-gnutls] libgcrypt] [ In reply to ]
Hi Werner !

Thanks for your response

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

But libgcrypt-1.4.1 gives core.

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


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

Hi,

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

union
{
PROPERLY_ALIGNED_TYPE dummy;
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.


Salam-Shalom,

Werner

--
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."
Re: [Fwd: Re: [Help-gnutls] libgcrypt] [ In reply to ]
On Tue, 27 May 2008 07:45, preeti.shandilya@aricent.com said:

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

Thanks. It seems that I would need to debug this. I have no such
machine available right now, so this is not easily possible.

Let's see whether other folks have such a problem too and are able to
track down the problem.


Salam-Shalom,

Werner

--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.


_______________________________________________
Gcrypt-devel mailing list
Gcrypt-devel@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gcrypt-devel