Hi ,
I am sorry to disturb you , but I do hope get some help from you .
I read article in
http://openssl.6102.n7.nabble.com/openssl-org-3592-bug-report-Crash-Critical-Security-bug-td55139i20.html
And I hit the same problem with my Asterisk11+OpenSSL 1.0.1
If there any
Checking compiler...
Running make...
make[1]: Entering directory '/tmp/openssl-1.0.2'
making all in crypto...
make[2]: Entering directory '/tmp/openssl-1.0.2/crypto'
making all in crypto/objects...
make[3]: Entering directory '/tmp/openssl-1.0.2/crypto/objects'
make[3]: Nothing to be done for
On Thu, Jan 22, 2015 at 11:34:35PM +0100, Steffen Nurpmeso wrote:
Since noone else seems to say a word.
I personally didn't understand at all why v1.0.2 when its
end-of-life is in sight already. Now you have to continue to
track three active branches. But this is your problem of course.
Since noone else seems to say a word.
I personally didn't understand at all why v1.0.2 when its
end-of-life is in sight already. Now you have to continue to
track three active branches. But this is your problem of course.
What i _really_ don't understand is why 1.0.2 is delivered with
false
On Thu Jan 22 22:48:19 2015, shane.bre...@securitease.com wrote:
t1_lib.o t1_lib.c
t1_lib.c: In function ‘tls1_get_curvelist’:
t1_lib.c:473:17: error: invalid type argument of unary ‘*’ (have
‘size_t’)
*pcurveslen = sizeof(fips_curves_default);
^
Fixed now, thanks for the report.
Steve.
--
http://www.openssl.org/about/releasestrat.html
Version 1.0.1 will be supported until 2016-12-31.
Perhaps its a matter of semantics, but isn't that EOL?
- Original Message -
From: Viktor Dukhovni openssl-us...@dukhovni.org
[stuff deleted]
You're confused. EOL has been announced
On Fri, Jan 23, 2015 at 05:44:19AM +, no_spam...@yahoo.com wrote:
http://www.openssl.org/about/releasestrat.html
Version 1.0.1 will be supported until 2016-12-31.
Perhaps its a matter of semantics, but isn't that EOL?
It will be in 2017.
--
Viktor.
