For what it's worth, here are all the functions with over 4Kb of stack usage
(at least, the way I compiled/analyzed it) for OpenSSL-0.9.6c.
4108 PKCS7_decrypt
4124 SMIME_text
4236 PKCS7_verify
4252 PKCS12_pbe_crypt
4268 PKCS12_decrypt_d2i
4268 PKCS12_i2d_encrypt
4380 PKCS5_pbe2_set
4764
Greetings,
This message has been automatically generated in response to the
creation of a trouble ticket regarding:
"Legalizing OpenSSL in France",
a summary of which appears below.
There is no need to reply to this message right now. Your ticket has been
assigned an ID
[[EMAIL PROTECTED] - Thu May 9 22:13:32 2002]:
> I am trying to compile on a 64 bit Suse sles7 powerpc system.
> the error message indicates
>
> -m486
>
> is an invalid compiler parameter. Anyone know the parameters I need to
give
> ./config to
> get it to work for 64 bit Suse on a powerpc???
On Thu, 9 May 2002, John Bihlmeyer via RT wrote:
>
> Hello to all,
> I am trying to compile on a 64 bit Suse sles7 powerpc system.
> the error message indicates
>
> -m486
>
> is an invalid compiler parameter. Anyone know the parameters I need to give
> ./config to
> get it to work for 64 bit Su
In message <[EMAIL PROTECTED]> on Thu, 09 May 2002 14:06:26
-0600, "Verdon Walker" <[EMAIL PROTECTED]> said:
VWalker> make the buffer allocated on the stack a more reasonable size
VWalker> - say 1 or 2k.
For everyone's info, I just decided to do exactly that. The buffer in
question has diminis
Hello to all,
I am trying to compile on a 64 bit Suse sles7 powerpc system.
the error message indicates
-m486
is an invalid compiler parameter. Anyone know the parameters I need to give
./config to
get it to work for 64 bit Suse on a powerpc
below are the results from running ./config with
It is always painful to admit when you are wrong, but hopefully I will
save at least some face by doing it now. You are correct that the static
buffer is used and dynamic buffer is only used when the static buffer
runs out of space.
In my defense, I did post an inquiry about the code before submi
>> The main make file does not use INSTALL_PREFIX in installing some of
>> the files in OPENSSLDIR.
>I'm probably blind... I'm looking at the current development branch
>(0.9.8-dev) and can't see where the use of INSTALL_PREFIX is missing.
It was pretty obvious to me when I reported the proble
[[EMAIL PROTECTED] - Thu Apr 25 16:16:02 2002]:
> Is this the expected behaviour ? Either way one must be fixed :)
> Btw EVP_OpenFinal does exactly what EVP_SealFinal does and adds to
> this the return value...
Hmm, I think Steve should answer this one. Personally, I think this
shows a certai
In message <[EMAIL PROTECTED]> on Wed, 08 May 2002 17:31:41
-0600, "Verdon Walker" <[EMAIL PROTECTED]> said:
VWalker> This patch fixes the routine BIO_vprintf in
VWalker> crypto\bio\b_print.c so that no longer allocates a 10k buffer
VWalker> on the stack that is never really used.
I just looked
10 matches
Mail list logo