On Wed, Oct 6, 2010 at 8:45 PM, Darryl Miles
darryl-mailingli...@netbauds.net wrote:
[SNIP]
Oh, and stdint.h is not available with all compilers!
Isn't this an ANSI requirement, ah well, poor compiler users what standards
do they conform to then ?
Like the safer string functions (strcpy_s
Dave may be right about there being no direct evidence for a read.
However I have since looked at the code the error is coming from and the error is being
reported at the time the SSL context is being interpreted, which doesn't mean the initial
loading of the SSL context wasn't error free as
First off: 64-bit filesys support would require a (minor?) API change;
there's been a similar size_t move in the past (partly rolled back IIRC) and
several 'int' or 'long' arguments should be turned into off_t types indeed,
irrespective of the typedef used to define that type. Several systems have
On 07-10-2010 08:28, Jeffrey Walton wrote:
On Wed, Oct 6, 2010 at 8:45 PM, Darryl Miles
darryl-mailingli...@netbauds.net wrote:
[SNIP]
Oh, and stdint.h is not available with all compilers!
Isn't this an ANSI requirement, ah well, poor compiler users what standards
do they conform to then
hi,
OS: Solaris 10 (Sun Fire T2000) (+ 10Recommended)
openssl: 0.9.8n from opencsw
apache: 2.2.15 compiled by Sun Studio 12 (+ lastest patches)
This combination coredumps several times a day:
# mdb ./core.httpd.29115
Loading modules: [ libc.so.1 libuutil.so.1 ld.so.1 ]
::stack
Forwarded to openssl-users for public discussion.
Best regards,
Lutz
- Forwarded message from Taint themexicanta...@gmail.com -
Date: Thu, 7 Oct 2010 10:48:15 -0400
Subject: cert problem
From: Taint themexicanta...@gmail.com
To: openssl-b...@openssl.org
I have been trying to
Hi,
I like to verify a S/MIME message with CMS_verify() (openssl-1.0.0a). If
the CMS structure does not contain a certificate and if I also cannot
provide the certificate, the verification fails. error:2E09D08A:CMS
routines:CMS_verify:signer certificate not found
I know that I need the
On 07-10-2010 17:27, Lutz Jaenicke wrote:
Forwarded to openssl-users for public discussion.
Best regards,
Lutz
- Forwarded message from Taintthemexicanta...@gmail.com -
Date: Thu, 7 Oct 2010 10:48:15 -0400
Subject: cert problem
From: Taintthemexicanta...@gmail.com
To:
On Thu, Oct 07, 2010, t...@compumatica.de wrote:
Hi,
I like to verify a S/MIME message with CMS_verify() (openssl-1.0.0a). If
the CMS structure does not contain a certificate and if I also cannot
provide the certificate, the verification fails. error:2E09D08A:CMS
routines:CMS_verify:signer
From: owner-openssl-us...@openssl.org On Behalf Of Kenneth Goldman
Sent: Tuesday, 05 October, 2010 18:32
I'm getting a PEM_write_PUBKEY() segfault. This is existing code
that works with 0.9.8 with Windows or 1.0.0. with Linux, but fails
with 1.0.0. and Windows.What's
From: owner-openssl-us...@openssl.org On Behalf Of Darryl Miles
Sent: Wednesday, 06 October, 2010 20:45
Very minor nits, but since we're being pedantic:
snip 64bit issues
The rules that you can trust are:
The ones mandated by the C language.
[From memory]
sizeof(char) == 1 (aka 8
Hi, everyone.
I've found that when a server built with
openssl-1.0.1-stable-SNAP-20101004 receives a Client Hello from a client
specifying TLS 1.0 (version = 0x0301), the connection is rejected for a
bad version. This appears to be implemented in ssl3_get_client_hello()
by:
if
12 matches
Mail list logo
