Thor Lancelot Simon wrote:
On Thu, Jun 09, 2011 at 05:08:30PM +0200, Ludwig Nussel wrote:
Thor Lancelot Simon wrote:
Again, I think this should be configured via an option on the SSL_CTX.
There is no way to set the default context options via config file
though, right? So every
On 09/06/2011 20:43, Andreas Probst wrote:
Hi community,
I found an email about VeraCode having found issues in OpenSSL (see
http://www.mail-archive.com/openssl-dev@openssl.org/msg25491.html).
Have there been follow-up activities? Did someone review or address
the VeraCode results?
is noone interested in this issue? i've sent this mail more than 2 months ago
and i haven't received a single response.
if this problem is abandoned (which is really sad coz this renders the truly
native windows version of openssl useless) then i need to unsubscribe from this
list coz i get a
On Wed, Jun 08, 2011, Thor Lancelot Simon wrote:
On Tue, Jun 07, 2011 at 10:58:20PM -0600, Guan Jun He wrote:
Hi, Openssl Developpers:
We have a platform with cryptographic hardware,and we try to take
advantage
of the platform's hardware cryptographic features.But openSSL
When the current effort to obtain a FIPS 140-2 validation began in
January we announced an expected completion in Q4 of this year, based on
our planned strategy of developing the FIPS module first, submitting it
for validation, and then developing the corresponding FIPS capable
OpenSSL 1.0.x.
The
On Fri, Jun 10, 2011 at 01:01:49PM +0200, Dr. Stephen Henson wrote:
There is SSL_OP_NO_COMPRESSION.
In that case, the suggestion to provide a config file setting for
default options seems particularly excellent.
Thor
__
Hi All,
I am Govind and I am currently working on a project, a part of which
involves validating certificates. I do have a cacert.pem file to check
against and I tried to verify using the openssl s_client command as below.
* openssl s_client -verify 100 -CAfile cacert.pem -showcerts -CApath ./
On Fri, Jun 10, 2011, Ben Laurie wrote:
Hmm. This looks like the start of a version fight between FIPS and
non-FIPS builds!
The ordinals will be synced between builds so anything in 1.0.1 has the same
ordinal in head. That can be done by just copying libeay.num from 1.0.1 to
HEAD before make
