Re: [openssl.org #848] Formatting problem in rand_add(1)

Hi Richard, Richard Levitte via RT schrieb: Care to tell us exactly what's wrong with it? There are more files where the name part spans several lines, for example des.pod, so I'm not sure why this specific file would be a problem... Please have a look at

Re: [openssl.org #846] [Fwd: Bug#224690: libssl0.9.7: minor spelling]

Hi Richard, Richard Levitte via RT schrieb: I don't think this bug report belongs with us, since it's a correction of the dpkg info template for OpenSSL... Do you mind if I kill this ticket? No, sorry for the wrong report. Christoph --

[openssl.org #852] Errors running OpenSSL under Windows 2000

Hello, I have installed OpenSSL 9.7c under Windows 2000, exactly as described in the file install.w32. I have changed my Microsoft Visual C++ settings as follows: 1. Project, Settings, Link, Object/Libary modules. In there I have added the two library files libeay32.lib and ssleay32.lib, and

[openssl.org #846] [Fwd: Bug#224690: libssl0.9.7: minor spelling]

[EMAIL PROTECTED] - Mon Mar 22 12:06:32 2004]: Hi Richard, Richard Levitte via RT schrieb: I don't think this bug report belongs with us, since it's a correction of the dpkg info template for OpenSSL... Do you mind if I kill this ticket? No, sorry for the wrong report. It's

RE: [openssl.org #849] WIN32 compile problems

Richard, Thanks for the email. Libeay32 linked fine. I got the problems when linking ssleay32. It complained about 2 unresolved symbols. I ended up copying the asn1_lib.obj line from the CRYPTOOBJ dependency section and pasting it into the SSLOBJ dependency section. That seemed to solve the

[openssl.org #849] WIN32 compile problems

[EMAIL PROTECTED] - Mon Mar 22 14:33:57 2004]: Richard, Thanks for the email. Libeay32 linked fine. I got the problems when linking ssleay32. It complained about 2 unresolved symbols. I ended up copying the asn1_lib.obj line from the CRYPTOOBJ dependency section and pasting it into

RE: [openssl.org #849] WIN32 compile problems

Richard, I guess you are right. I downloaded the latest openSSL (SNAP-20040322) and went through the same steps as before. I did not have to modify ntdll.mak at all. So disgregard my previous report about unresolved symbols. I did have to remove ENGINE_load_gmp from ms\libeay32.def

Re: [openssl.org #849] WIN32 compile problems

In message [EMAIL PROTECTED] on Mon, 22 Mar 2004 14:33:59 +0100 (MET), [EMAIL PROTECTED] via RT [EMAIL PROTECTED] said: rt Libeay32 linked fine. I got the problems when linking ssleay32. It rt complained about 2 unresolved symbols. I ended up copying the rt asn1_lib.obj line from the

Re: [openssl.org #849] WIN32 compile problems

In message [EMAIL PROTECTED] on Mon, 22 Mar 2004 14:33:59 +0100 (MET), [EMAIL PROTECTED] via RT [EMAIL PROTECTED] said: rt Libeay32 linked fine. I got the problems when linking ssleay32. It rt complained about 2 unresolved symbols. I ended up copying the rt asn1_lib.obj line from the

Patches for z/OS System Programming C (SPC) Environment

Hi, I put together a collection of patches to get openssl 0.9.7c working under z/OS System Programming C (SPC) Environment: Part of the patches is obtained from http://www.openldap.org/faq/data/cache/745.html The rest of the patches is to work around the fact that most of the POSIX function

[openssl.org #853] serial/index file handling broken on Windows in 0.9.7d

Re: openssl-dev thread: New CA index subfiles (.attr, .attr.new, .attr.old, .new) OpenSSL 0.9.7d introduces a bug on Windows in the openssl executable in relation to the renaming of temporary serial and index files. The renames are failing since the special WIN32_rename() function (which

OpenSSL 097d compile error in WinCE build

Openssl 097d with WinCE build has syntax error. clarm.exe /Fotmp32_ARM\apps.obj -DMONOLITH -Iinc32 [Chris Brook]Itmp32_ARM /W3 /WX /Ox /O2 /Ob2 /Gs0 /GF /Gy /nologo -DWCEPLATFORM=MS_POCKET_PC_2000 -DARM -D_ARM_ -DUNDER_CE=300 -D_WIN32_CE=300 -DUNICODE -D_UNICODE -DWIN32

FW: OpenSSL 097d compile error in WinCE build

Sorry I hit send accidentally. Let's try again. We also tried compiling without the /Gs0 option as Steven Reddie suggested and that made no difference. Chris BrookOpenssl 097d with WinCE build has syntax error. clarm.exe /Fotmp32_ARM\apps.obj -DMONOLITH -Iinc32 -Itmp32_ARM /W3 /WX /Ox /O2

Memory leak in Apache/mod_ssl/OpenSSL

Title: Memory leak in Apache/mod_ssl/OpenSSL After tagging the OPENSSL_malloc/CRYPTO_malloc memory allocation calls and running tests over the weekend calls to OPENSSL_malloc in the following files failed to release memory by calling the corresponding OPENSSL_free: bn_bind.c - 494,788

[openssl.org #854] randfile.c doesn't complile on some platforms

Due to the inclusion of S_IFBLK logic in RAND_write_file (crypto/rand/randfile.c) a later declaration of int fd =... fails to compile on some older, stricter, compiliers. see patch for solution, basicly a declaration of int fd located with the other declarations.

[PATCH] add Interix configuration

Greetings, Enclosed below please find the output of 'diff -u' for the two files Configure and config. The additions listed in these two files add configuration support for Interix. This covers the previous release, 3.0, which did not have pthreads, and the current and likely future releases which

a bug in RSA_public_encrypt with RSA_NO_PADDING

Hi, int RSA_public_encrypt(int flen, unsigned char *from, unsigned char *to, RSA *rsa, int padding); It seems that there is a bug in RSA_public_encrypt with the padding method set as RSA_NO_PADDING. The bug is: when flen is not the RSA key size (e.g., 32 bytes), the function returns -1 and

Patch to support -crlsecs in openssl ca command

Title: Message Hi All, I've attached a simple patch (against 0.9.7d) which adds support for -crlsecs to the ca command. This is useful for testing of components that automatically fetch updated CRLs as they expire -- the current granularity of an hour makes for a long test. Regards,