sed -i 's/-DTERMIO/-DTERMIOS/g' Configure
Daniel
2014-06-05 4:13 GMT+02:00 Mingkai Xuan ricky@gmail.com:
Hi, guys
I download the latest openssl library. the version is 1.0.1g.
and download musl libc at the same time. it 's at version 1.1.1.
the following configure command:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL Security Advisory [05 Jun 2014]
SSL/TLS MITM vulnerability (CVE-2014-0224)
===
An attacker using a carefully crafted handshake can force the use of weak
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL Security Advisory [05 Jun 2014]
Resend: first version contained characters which could cause signature failure.
SSL/TLS MITM vulnerability (CVE-2014-0224)
===
On Thu, Jun 05, 2014, OpenSSL wrote:
OpenSSL Security Advisory [05 Jun 2014]
Resend: first version contained characters which could cause signature
failure.
Oops, something else to add to the list of things to double check before
making a
Hello,
I have implemented an SSL server on the ecos platform and it seems to be
working well however I am a tiny bit unclear about the requirements around
whether or not calls to SSL_read and SSL_write need to be syncrhonized and I
want to avoid doing something incorrect. The specific question
Hello,
I have implemented an SSL server on the ecos platform and it seems to be
working well however I am a tiny bit unclear about the requirements around
whether or not calls to SSL_read and SSL_write need to be syncrhonized and I
want to avoid doing something incorrect. The specific question
Just a bit of clarification on my question... I am fully aware that if the
OpenSSL library tells me it NEEDS_READ or NEES_WRITE in response to an SSL_read
I should then issue that same SSL_read command again with the same parameters
when the associated resource is ready for whichever operation
First of all, I think you should ask this question on
openssl-us...@openssl.org.
In my opinion you can mix SSL_write() and SSL_read() operations when
they return WANTS_X.
According to documentation of SSL_read() says The calling process then
must repeat the call after taking appropriate
I'm sorry, i will switch DLs... i'm new to this forum!
Thanks for the information!
From: owner-openssl-...@openssl.org [owner-openssl-...@openssl.org] on behalf
of Krzysztof Kwiatkowski [krzys...@leeds.pl]
Sent: Thursday, June 05, 2014 1:09 PM
To:
On 06/04/2014 04:58 PM, Mike Bland wrote:
Thanks to a few brave volunteers and the support of the core OpenSSL
team, it looks like we can begin moving on this effort soon. I've
begun to document the current state of things on the wiki:
http://wiki.openssl.org/index.php/Unit_Testing
There's
Hello,
it would be nice, if you remove the march=i486 for Cygwin in Configure, Thank
you!
Configure:
Cygwin, gcc:-DTERMIOS -DL_ENDIAN -fomit-frame-pointer -O3 -march=i486
-Wall:::CYGWIN32::BN_LLONG ${x86_gcc_des}
${x86_gcc_opts}:${x86_asm}:coff:dlfcn:cygwin-shared:-D_WINDLL:-shared:.dll.a,
File ssl/s3_pkt.c uses INT_MAX since May 19th. This macro is defined in
limits.h which is not included in s3_pkt.c.
Some platforms have INT_MAX defined even without the include - like
Linux - others not - like Solaris.
Similar files like e.g. ssl/s3_both.c already include limits.h.
The problem
Commit 989d87cb1a174a951efd829ff6b2f68a322f9df8 for 1.0.1 was shortly
after improved by commit dac3654e2d89d43807e7b8e4b9da86ae1d33fe2b. It
changed s-s3-wnum INT_MAX to s-s3-wnum = INT_MAX (lower or
equals instead of lower than).
The backports to 1.0.0 and 0.9.8 only contained the first commit,
Hi,
When building the 1.0.1h release I got this error:
heartbeat_test.o: In function `set_up':
test/heartbeat_test.c:94: undefined reference to `ssl_init_wbio_buffer'
test/heartbeat_test.c:102: undefined reference to `ssl3_setup_buffers'
heartbeat_test.o: In function `set_up_dtls':
On Thu, Jun 5, 2014 at 2:41 PM, Kurt Roeckx via RT r...@openssl.org wrote:
Hi,
When building the 1.0.1h release I got this error:
heartbeat_test.o: In function `set_up':
test/heartbeat_test.c:94: undefined reference to `ssl_init_wbio_buffer'
test/heartbeat_test.c:102: undefined reference to
On Thu Jun 05 20:40:49 2014, rainer.j...@kippdata.de wrote:
File ssl/s3_pkt.c uses INT_MAX since May 19th. This macro is defined in
limits.h which is not included in s3_pkt.c.
+#include limits.h
#include stdio.h
#include limits.h
Hmmmlook two lines down from where you've added an
One correction to self: no problem for 1.0.1, which had been fixed in
commit 8ca7d124304502158fba780eed293c4e3c5c1c71 Fixed Windows
compilation failure.
But 1.0.0 and 0.9.8 lack tha addition.
__
OpenSSL Project
Hi Reini,
Actually, I was asking for thoughts on whether to create a separate
openssl-testing mailing list, which I'm leaning towards at the moment,
as I plan to get very chatty with the volunteers helping with unit
testing.
That said, I've limited experience with valgrind. Are you volunteering
On 05/06/14 20:08, Rainer Jung wrote: One correction to self: no problem for
1.0.1, which had been fixed in
commit 8ca7d124304502158fba780eed293c4e3c5c1c71 Fixed Windows
compilation failure.
But 1.0.0 and 0.9.8 lack tha addition.
I have back ported the commit to 1.0.0 and 0.9.8
Matt
On 6/5/2014 3:06 PM, Matt Caswell via RT wrote:
On Thu Jun 05 20:40:49 2014, rainer.j...@kippdata.de wrote:
File ssl/s3_pkt.c uses INT_MAX since May 19th. This macro is defined in
limits.h which is not included in s3_pkt.c.
+#include limits.h
#include stdio.h
#include limits.h
Hmmmlook two
On Thu, Jun 05, 2014 at 04:43:44PM +0200,
alexander.elg...@external.t-systems.com wrote:
Hello,
it would be nice, if you remove the march=i486 for Cygwin in Configure,
Thank you!
Configure:
Cygwin, gcc:-DTERMIOS -DL_ENDIAN -fomit-frame-pointer -O3 -march=i486
On Thu, Jun 05, 2014 at 03:01:47PM -0400, Mike Bland wrote:
On Thu, Jun 5, 2014 at 2:41 PM, Kurt Roeckx via RT r...@openssl.org wrote:
Hi,
When building the 1.0.1h release I got this error:
heartbeat_test.o: In function `set_up':
test/heartbeat_test.c:94: undefined reference to
From: Kurt Roeckx [mailto:k...@roeckx.be]
Sent: Thursday, June 05, 2014 9:34 PM
On Thu, Jun 05, 2014 at 04:43:44PM +0200, Alexander.Elgert@external.t-
systems.com wrote:
it would be nice, if you remove the march=i486 for Cygwin in
Configure, Thank you!
Configure:
Cygwin,
Hi Mike
On Sun Apr 27 13:04:20 2014, vap...@gentoo.org wrote:
It's a standard setting that other build systems use.
Can you explain why you need this?
@@ -217,6 +217,7 @@ BUILDENV= PLATFORM='$(PLATFORM)'
PROCESSOR='$(PROCESSOR)' \
MAKEDEPEND='{TOP}/util/domd {TOP} -MD
On 05/06/14 21:51, Jeremy Farrell wrote:
Current OpenSSL sources only support 32-bit Cygwin. Corinna Vinschen
contributed patches to support 64-bit Cygwin some time ago:
http://rt.openssl.org/Ticket/Display.html?id=3110
These patches have already been applied to the 1.0.2 branch by Andy.
On Thu Jun 05 20:41:05 2014, k...@roeckx.be wrote:
This is probably related to me not exporting those symbols as they are
marked local.
Kurt
Is this related to the way you build the Debian packages? We are likely to see
a lot more like this as Mike's test team get going. In unit testing its
On Thu, Jun 05, 2014 at 11:34:15PM +0200, Matt Caswell via RT wrote:
On Thu Jun 05 20:41:05 2014, k...@roeckx.be wrote:
This is probably related to me not exporting those symbols as they are
marked local.
Kurt
Is this related to the way you build the Debian packages?
Yes. And this is
On Thu, Jun 05, 2014 at 11:34:15PM +0200, Matt Caswell via RT wrote:
On Thu Jun 05 20:41:05 2014, k...@roeckx.be wrote:
This is probably related to me not exporting those symbols as they are
marked local.
Kurt
Is this related to the way you build the Debian packages?
Yes. And this is
On Thu Jun 05 23:42:31 2014, k...@roeckx.be wrote:
We are likely to see
a lot more like this as Mike's test team get going. In unit testing
its okay
to access internal symbols.
But then you shouldn't link to the shared library. The static
library probably works.
Any chance you can
--On Thursday, June 05, 2014 4:33 PM -0400 Ray Satiro raysat...@yahoo.com
wrote:
I think maybe he just added it twice because it is missing. I noticed the
same thing when I tried to build this afternoon.
Definitely wasn't added twice, you can see it is native to openssl-1.0.1h.
In fact, it
On Thu 05 Jun 2014 22:53:32 Matt Caswell via RT wrote:
On Sun Apr 27 13:04:20 2014, vap...@gentoo.org wrote:
It's a standard setting that other build systems use.
Can you explain why you need this?
because people want to set custom linker flags. `man ld` shows quite a large
number that
On Thu 05 Jun 2014 22:53:32 Matt Caswell via RT wrote:
On Sun Apr 27 13:04:20 2014, vap...@gentoo.org wrote:
It's a standard setting that other build systems use.
Can you explain why you need this?
because people want to set custom linker flags. `man ld` shows quite a large
number that
32 matches
Mail list logo
