On Fri, Dec 03, 2004 at 11:49:22AM +0100, Michael Jung wrote:
Greetings, Michael
Changelog: Added a missing break in encrypt_block_impl
Index: dlls/rsaenh/implglue.c
JFYI,
we (Novell) are now working on reapproving WINE for US export due to your cryptographic library import.
I will keep you posted, but I expect approval.
Actually, in the closest meaning of the export regulations, I am not even allowed to build RPMs for SourceForge anymore here at SUSE/Novell :(
Fun without end, I had hoped we keep openssl dynamic linking ;)
Ciao, Marcus
On Friday 03 December 2004 13:06, Marcus Meissner wrote:
Actually, in the closest meaning of the export regulations, I am not even allowed to build RPMs for SourceForge anymore here at SUSE/Novell :(
Fun without end, I had hoped we keep openssl dynamic linking ;)
Sorry, I didn't mean to cause problems for anybody. Actually, I would not have a problem with going back to an OpenSSL based implementation. It's just that there were some compilation problems with older RH versions (which I think would not be hard to resolve) and if I remember correctly, the ReactOS project has some license problems with OpenSSL.
We could also make the selection between OpenSSL/LibTomCrypt a compile time option (Although, as I understand it, we don't want to many of those, right?)
Bye, Michael
On Fri, Dec 03, 2004 at 01:40:42PM +0100, Michael Jung wrote:
On Friday 03 December 2004 13:06, Marcus Meissner wrote:
Actually, in the closest meaning of the export regulations, I am not even allowed to build RPMs for SourceForge anymore here at SUSE/Novell :(
Fun without end, I had hoped we keep openssl dynamic linking ;)
Sorry, I didn't mean to cause problems for anybody. Actually, I would not have a problem with going back to an OpenSSL based implementation. It's just that there were some compilation problems with older RH versions (which I think would not be hard to resolve) and if I remember correctly, the ReactOS project has some license problems with OpenSSL.
We could also make the selection between OpenSSL/LibTomCrypt a compile time option (Although, as I understand it, we don't want to many of those, right?)
No worries. I expect no problems ;)
Ciao, Marcus