I'm using the PKCS#7 functions to append signatures to files we're sending
over the Internet and it works fine. We're planning to do some encryption
also. The main difficulty is to uderstand and use properly these functions.
Thank god, there has always been a good support from this mailing list,
Can someone tell me what is the (approximate) date of the next openssl
release (0.9.6)?
Thanks
Richard Dykiel
www.adero.com
978-287-5560 x289
__
OpenSSL Project http
Steve, thanks.
I'd be interested if someone knows any tool capable of detecting memory
leaks on Linux that I could use on an Openssl app; apparently Purify doesn't
have a Linux version.
Some precisions below:
My application calls directly the following functions in OpenSSL:
*
I've had no answers to that question so far, so I'm re-posting it, hoping
that someone out there could provide me with a hint...
thanks
-Original Message-
From: Richard Dykiel [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 13, 2000 11:36 AM
To: [EMAIL PROTECTED] (E-mail)
Subject
:
* EVP_DecryptFinal: Bad Decrypt
* PEM_do_header: Bad Decrypt
Thanks..
Richard Dykiel
www.adero.com
978-287-5560 x289
__
OpenSSL Project http://www.openssl.org
User Support Mailing List
Hello,
I'd appreciate a hint on the following:
when calling ERR_error_string, I dont geta readable error string, but
rather:
error:0906D06C::lib(9) :func(109)
:reason(108)error:0B06F009::lib(11) :func(111)
:reason(9)error:2106B00B::lib(33) :func(107) :reason(11)
I call
24, 2000 11:01 PM
Subject: Re: pkcs7 encryption limited by memory?
Richard Dykiel wrote:
Hello,
I am studying how pkcs7 works in openssl, particularly for encryption
(enveloped data). Except if I made a mistake, it seems that pkcs7
encryption is made in memory, hence precluding
Hello,
I am studying how pkcs7 works in openssl, particularly for encryption
(enveloped data). Except if I made a mistake, it seems that pkcs7 encryption is
made in memory, hence precluding encrypting very huge files: am I right?
Say you want to envelop a file:
- PKCS7_dataInit returnsa BIO
Hi
we plan to use the PKCS#7 module to signt + encrypt data.
In the readme file of the crypto/pkcs7 directory we can read:
"WARNING
Everything in this directory is experimental and is subject to
change.
Do not rely on the stuff in here not changing in the next release"
I'd be very grateful
I provided an explanation on this (see attached message). I dont know if
Konstantin succeeded in working qround that bug. I dont know what Windows
experts think of my explanations either.
- Original Message -
From: jose antonio garvayo [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent:
Hello,
generating dsa params w/ the following command line:
openssl dsaparam -rand rand.txt -out keys\dsa2.par 1024
I Get the following message:
unable to write 'random state'
However the dsa parameter file has been created and is usable. Must be
something obvious?
Hello,I create dsa self-signed certs with the following
sequence:
openssl dsaparam -rand rand.txt -out keys\dsa2.par
1024openssl req -config CAconf.conf -x509 -newkey dsa:keys\dsa2.par
-keyout keys\dsa2.prk -out certs\dsass2.pem -days 730 -extensions v3_ca -passin
pass:MyTailorIsRich
specific */
#endif
}
- Original Message -
From: Bodo Moeller [EMAIL PROTECTED]
To: Richard Dykiel [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Wednesday, March 15, 2000 8:11 PM
Subject: Re: memory leaks in SSLeay_add_all_algorithms?
Richard Dykiel [EMAIL PROTECTED]:
Hello, the simple piece
- Original Message - Anyway, saying that OpenSSL doesn't leak *in
debug mode* is not
entirely true. The memory debugging code does create at least one
hash table and at most two, and it never free's them. I've been
pondering adding a CRYPTO_mem_cleanup() or something like that, but
That's strange, I used the following command without problems:
openssl x509 -in certs\user1.pem -inform PEM -out certs\user1.cer -outform
DER
What's the error exactly?
- Original Message -
From: Lenya Khachaturov [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, March 16, 2000
B5 40 00 41 00 00 00
Object dump complete.
This will make it easier for me to identify my leaks.
Thanks.
- Original Message -
From: Bodo Moeller [EMAIL PROTECTED]
To: Richard Dykiel [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Thursday, March 16, 2000 4:42 PM
Subject: Re: memory leaks
specific */
#endif
}
- Original Message -
From: Bodo Moeller [EMAIL PROTECTED]
To: Richard Dykiel [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, March 16, 2000 5:18 PM
Subject: Re: memory leaks in SSLeay_add_all_algorithms?
On Thu, Mar 16, 2000 at 05:31:50PM -0500, Richard Dykiel
Hello, the simple piece of code below results in "4243 bytes leaked in 280
chunks" as reported by the CRYPTO debug memory functions.
Most leaks are caused by the call to SSLeay_add_all_algorithms.
Some leaks are caused by the calls to the CRYPTO debug memory functions,
but I can live with
Sorry if this seems trivial, but:
1- I created a root cert (self signed)
2- I created a cert request for a CA cert
3- I made my CA cert signed by my root cert:
it signed, but could not verify
I guessed it's because my root cert has not been installed as a "trusted"
root.
I' trying to set my
Hello,
I'm using the openssl utility to create a set of certificates.
I created a root certificate.
Now I'm trying to createa certifiate request for an intermediate CA
(it would be signed by my root certificate).
The command I use is:
openssl req -config CAconf.conf -newkey rsa:1024 -outform
Have you tried to create a Visual Studio project of type "makefile"? It's
easy to use the OpenSSL makefiles as they are. You can compile from the IDE,
jump to correct errors from the build window, start debugging sessions on
executables (trickier), etc...
Having an external makefile does not
Ulf,
just to mention, the REQ part of the documentation is not accessible from
the index page of the OpenSSL web site http://www.openssl.org/docs/
Maybe other interesting existing documents are not accessible too. As a
newcomer in OpenSSL, I wish they would.
Thanks.
- Original Message
22 matches
Mail list logo