Hello Openssl-dev team,
Currently am checking whether Renegotiation is enabled in openssl 0.9.8q
version. If enabled, would like to disable this.
As per release note, i see
*Changes between 0.9.8k and 0.9.8l [5 Nov 2009]*
*) Disable renegotiation completely - this fixes a severe security
Hello Openssl dev team,
Currently we are using openssl 0.9.8q version. Earlier we have used openssl
0.9.8k.
We have seen change in the return value handling of ssl_verify_cert_chain()
at function ssl3_get_client_certificate().
At openssl 0.9.8k, ssl_verify_cert_chain() is handled like this
Sorry team. Change observed between openssl 0.9.8g to openssl0.9.8k
Can you please tell us the intent of this change and how we can get out of
this problem.
Regards,
Rajeswari
On Thu, Sep 26, 2013 at 3:18 PM, Rajeswari K raji.kotamr...@gmail.comwrote:
Hello Openssl dev team,
Currently we
On Wed, Sep 25, 2013, Fili, Tom wrote:
I'm using the capi API to access certificates in the Windows Cert Store. I'm
using the following to get access to the private key
EVP_PKEY *key = ENGINE_load_private_key(e, subject, 0, 0);
This seems to work as far as I can tell. Even if the
Hello!
I'm currenty working with openssl-0.9.8.y. As we can see in the changelog
in the official openssl page there is a correct fix concerning
the CVE-2013-0169 which is only available at version openssl-1.0.1.e.
My question is when do you plan to included this change at the series
0.9.8??
Is
hu nice to know, thanks David! i will check this file
2013/9/25 David Johnston d...@deadhat.com
On 9/25/2013 2:19 PM, Roberto Spadim wrote:
hi david!
do you have a patch about this hack?
Actually Fedora 18 fixes the primary problems. It has an update to rngd so
that it uses RdRand
Hi,
I just created a key pair using:
RSA *rsa = RSA_generate_key(bits, RSA_F4, NULL, NULL);
assert(rsa);
...
EVP_PKEY *pkey = EVP_PKEY_new();
assert(EVP_PKEY_assign_RSA(pkey, rsa));
Now I want to get the public key in PEM format:
assert(EVP_PKEY_type(pkey-type) == EVP_PKEY_RSA);
On Thu, Sep 26, 2013, Costas Stasimos wrote:
Hello!
I'm currenty working with openssl-0.9.8.y. As we can see in the changelog
in the official openssl page there is a correct fix concerning
the CVE-2013-0169 which is only available at version openssl-1.0.1.e.
My question is when do you
I have a similar problem and have found a fix for it. Please see the
thread below to see if your problem is the same:
http://www.mail-archive.com/openssl-dev@openssl.org/msg33010.html
Benson Kwok
Development
Www.air-watch.com
On 9/25/13 6:35 PM, Roger Miller roger.mil...@oracle.com wrote:
Hmmm...ok. Is it possible that in some cases passing the subject to
ENGINE_load_private_key is the incorrect thing to do?
What I'm doing seems pretty simple but in some cases I get key/value mismatch
errors.
I get the PCCERT_CONTEXT from the windows certificate store.
Then do the following to
The message below gut truncated somehow. Again:
The OpenSSL wiki states that there is support for built-in standard sets of
Diffie-Hellman parameters (see link below). However, I was unable to find any
documentation about which sets of parameters those actually are - short of
browsing the
HI,
I am running the speed option to measure the performance difference
between 0.9.8y and 1.0.0k AES implementations. There seems to be a
noticeable difference in the performance results between the two versions
when I run 'openssl speed aes' on my MacBook. I see a performance
degradation
-Original Message-
From: bensonkwok...@air-watch.com [mailto:bensonkwok...@air-watch.com]
I have a similar problem and have found a fix for it. Please see the
thread below to see if your problem is the same:
http://www.mail-archive.com/openssl-dev@openssl.org/msg33010.html
On Thu, Sep 26, 2013, Fili, Tom wrote:
Hmmm...ok. Is it possible that in some cases passing the subject to
ENGINE_load_private_key is the incorrect thing to do?
What I'm doing seems pretty simple but in some cases I get key/value mismatch
errors.
I get the PCCERT_CONTEXT from the
14 matches
Mail list logo
