On 2012-09-27 07:19 +0200 (Thu), sa...@zxid.org wrote:
> Once you are past the accept handshake, the reading and writing are
> unidirectional per thread and this should be possible to make
> work. But of course it is possible that a new handshake happens
> in midconnection.
As you point out, in t
Curt Sampson said:
> On 2012-09-25 16:48 +0200 (Tue), sa...@zxid.org wrote:
>
> > ...I get an abort with following error
> > int_thread_release, bad reference count
> >
> > 3. I have multiple worker threads synchronized such that one thread
> >may be reading while other is writing, but never
On 2012-09-25 16:48 +0200 (Tue), sa...@zxid.org wrote:
> ...I get an abort with following error
> int_thread_release, bad reference count
>
> 3. I have multiple worker threads synchronized such that one thread
>may be reading while other is writing, but never two threads
>simultaneously r
On 2012-09-24 20:55 + (Mon), Nou Dadoun wrote:
> Quick question: is there a simple openssl api call which will tell me
> if an x509 certificate is self-signed? ... N
Will simply comparing the issuer and the subject DNs in the cert do what
you need? Or do you need to check validity, the Author
> From: owner-openssl-us...@openssl.org On Behalf Of sa...@zxid.org
> Sent: Wednesday, 26 September, 2012 06:46
> Matthias Apitz said:
> > and was a bit surprised that the connection went fine and
> the "wserver"
> > accepts the SSL connection and responds fine with its dummy
> message. The
> >
>From: owner-openssl-us...@openssl.org On Behalf Of Bogdan Harjoc
>Sent: Wednesday, 26 September, 2012 12:23
>I'm looking for the reason a server closes a SSL connection unless
>I overwrite this cipher id from the ClientHello cipher list:
(more exactly, improperly closes during handshake; "close
You're probably using a much more recent version of the tool-chain, headers,
and libraries than that version of OpenSSL was developed with - it was released
nine or so years ago. One way would be to get hold of tools and headers which
were in use back then. Another is to go through the sources a
Le 25/09/2012 18:45, Jakob Bohm a écrit :
On 9/25/2012 6:12 PM, Erwann Abalea wrote:
Le 25/09/2012 14:16, Jakob Bohm a écrit :
> On 9/25/2012 11:11 AM, Erwann Abalea wrote:
[...]
Any signature algorithm works by dividing the universe of N bit strings
into those that are validsignatures for the
Bonsoir,
Your public key parameter field is set to NULL. It must either be an OID
to name the curve, or explicit parameters.
--
Erwann ABALEA
Le 26/09/2012 14:17, Naveen Gopala Reddy a écrit :
Hi,
I am using openssl version 1.0.1c to parse the attached
certificate(test.pem) using the below
On Wed, Sep 26, 2012, Michel wrote:
> Hello,
>
> I am using the the OpenSSL enc command to encrypt and decrypt a test file.
> When using AES-GCM mode, I can encrypt but cannot decrypt the result.
> Even though I succeed with all other modes.
>
> Example is as follow :
> openssl enc -e -a -aes-12
Hello,
I am using the the OpenSSL enc command to encrypt and decrypt a test file.
When using AES-GCM mode, I can encrypt but cannot decrypt the result.
Even though I succeed with all other modes.
Example is as follow :
openssl enc -e -a -aes-128-gcm -nosalt -p -K
28C65581AABBBA0EBFC1DB5D5C614FE
Erik Tkal said:
> Wouldn't the binary compatibility only work the other way? I.e. if you have
> an app written against 1.0.0 and then later drop in 1.0.1 binaries (since
> maybe some other app needs that), then that should work and your app should
> not break.
>
> If you compile against 1.0.1
Wouldn't the binary compatibility only work the other way? I.e. if you have an
app written against 1.0.0 and then later drop in 1.0.1 binaries (since maybe
some other app needs that), then that should work and your app should not break.
If you compile against 1.0.1 headers wouldn't the assumpti
"Dr. Stephen Henson" said:
> On Tue, Sep 25, 2012, Thakur, Praveen Kumar wrote:
>
> > I don't see any issue if .so files extension is 1.0.0. However, I wanted to
> > confirm that is this a defect with 1.0.1 release? Or am I missing something.
>
> The 1.0.1 release should be binary compatible wi
On Tue, Sep 25, 2012, Thakur, Praveen Kumar wrote:
> I don't see any issue if .so files extension is 1.0.0. However, I wanted to
> confirm that is this a defect with 1.0.1 release? Or am I missing something.
The 1.0.1 release should be binary compatible with 1.0.0, any discrepancies
should be fi
On Tue, Sep 25, 2012, blaan...@rockwellcollins.com wrote:
>
> After further investigation, the FIPS private headers (for instance,
> fipssyms.h) are definitely being installed when I do "make install" in the
> openssl-fips-2.0.1 directory. Then those headers are being used by my
> openssl build,
Apologies for repeated top-posting. Only have crappy web-access.
See:
http://stackoverflow.com/questions/3242386/error-compiling-openssl-for-win32
[1]
You can locally fix up Op4enSSL's e_os.h to remove conflicts or find
another way to to do. I think the /G5 is being ignored.
Well, as the messages say, you specified /WX - "treat any warning as a fatal
error." You got a warning -- /G5 is deprecated - and, just as you asked, VC
treated it as a fatal error.
Charles
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Ahmad
Sent:
I can report that using code compiled with 1.0.1c headers against
dynamic link libraries from 1.0.0 (from debian) causes reference
count errors. I solved this by statically linking openssl-1.0.1c to
avoid any mismatch (my recent bugreport about reference count
problem is already statically linked s
One more significant peculiarity of my situation I forgot to mention:
7. I am using ClientTLS authentication (using self signed cert)
Cheers,
--Sampo
sa...@zxid.org said:
> With OpenSSL-1.0.1c downloaded from openssl.org and compiled from source
> on x86 Linux 2.6 (LinuxMint 12) using gcc-4.6.1,
Matthias Apitz said:
> and was a bit surprised that the connection went fine and the "wserver"
> accepts the SSL connection and responds fine with its dummy message. The
> openssl client does not need any key files to connect...
In normal SSL, only the server needs certificate and private key. In
Hi Praveen,
I guess you are integrating fips compliant. I have a
question that how to call FIPS_mode_set(1), in our code as I am new to
ANDROID NDK. I have not seen any question regarding this , can you please
help me in this regard.
Thanks,
kondlada
On Tue, Sep 25, 2012 at 8:
Hello,
I'm on the way to change some TCP/IP client server application to use
Openssl to cipher the traffic. To get understanding of Openssl I started
with the openssl-examples-20020110 some weeks ago. After
struggling some time with the way of creating the CA and certificate
(because the ones in
I am having some error when i try to install openssl-0.9.7d.
from the VC++ environment at a prompt when i run this command
> nmake -f ms\ntdll.mak
I get following errors
1 file(s) copied.
cl /Fotmp32dll\cryptlib.obj -Iinc32 -Itmp32dll /MD /W3 /WX /G5 /Ox
/O2
/Ob2 /Gs0 /GF /Gy
With OpenSSL-1.0.1c downloaded from openssl.org and compiled from source
on x86 Linux 2.6 (LinuxMint 12) using gcc-4.6.1, I get an abort with
following error
int_thread_release, bad reference count
Analyzing situation...
(gdb) bt
#0 0x00920416 in __kernel_vsyscall ()
#1 0x0037ac8f in raise ()
I don't see any issue if .so files extension is 1.0.0. However, I wanted to
confirm that is this a defect with 1.0.1 release? Or am I missing something.
Thanks,
Praveen
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of karthik kondlada
Sent: Tuesday, Sept
26 matches
Mail list logo
