On Wed, Mar 18, 2015 at 5:14 AM, Matt Caswell m...@openssl.org wrote:
On 18/03/15 07:59, Jakob Bohm wrote:
(Resend due to MUA bug sending this to -announce)
On 16/03/2015 20:05, Matt Caswell wrote:
Forthcoming OpenSSL releases
The OpenSSL project team would
Hi,
My problem is if the string that I want to decode start with null
terminated char (as in a SSH pubkey), the base64_decode does not return
anything at all. The encoded string itself does not have null terminated
chars but rather the decoded result. The buffer being returned is empty.
How to
I just posted an updated version of my script in a new
thread, titled
Minimizing the pain of reformatting your OpenSSL patches
Regards,
msp
On 03/19/2015 02:22 AM, Dr. Matthias St. Pierre wrote:
Hello,
Here is a recipe to guide you through the reformatting.
It worked nicely for me. I
Copy Paste error:
The name of the new branch is
${upstream}-post-auto-reformat
not
${upstream}-pre-auto-reformat
msp
On 03/19/2015 09:40 AM, Dr. Matthias St. Pierre wrote:
For every commit on the rebased branch, it does an automatic
conversion, placing the results onto a new branch
Sorry for that, another typo:
Please replace OpenSSL_1_0_1k by OpenSSL_1_0_1m below.
On 03/19/2015 09:40 AM, Dr. Matthias St. Pierre wrote:
3) After the script has succeeded, you can rebase your
reformatted branch to the head of the stable branch or
to the tag of the most recent release, e.g.
Hello,
the upcoming security update imposes a special challenge to
all OpenSSL users who maintain their own patch sets.
The reason is the code reformat which has taken place in between
the last and the upcoming release, which renders existing patches
useless.
Hey I got this. Sorry I was confused with the length. BIO_read returns the
length which I was able to use to get the MD5. Problem solved!!!
Many thanks.
--Pashant
On 19 March 2015 at 14:24, Prashant Bapat prash...@apigee.com wrote:
Hi,
My problem is if the string that I want to decode start
Hello,
my original post contained two typos. Also, the script reversed the order
of the commits due to a forgotten '--reverse'. (Probably, it was too late,
last night ;)
So here comes a repost with all corrections. Sorry for the inconveniences.
Regards,
msp
--
Hello,
the upcoming
I am trying to use ECDH-RSA-AES256-SHA with ssl3 with s_client and s_server on
the master branch. (cloned at commit f7683aaf36341dc65672ac2ccdbfd4a232e3626d)
and then retested with a more recent clone: (commit
da27006df06853a33b132133699a7aa9d4277920).
We are running a test suite that tests
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OpenSSL Security Advisory [19 Mar 2015]
===
OpenSSL 1.0.2 ClientHello sigalgs DoS (CVE-2015-0291)
=
Severity: High
If a client connects to an OpenSSL 1.0.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OpenSSL version 0.9.8zf released
===
OpenSSL - The Open Source toolkit for SSL/TLS
http://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 0.9.8zf of our open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OpenSSL version 1.0.1m released
===
OpenSSL - The Open Source toolkit for SSL/TLS
http://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.0.1m of our open source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OpenSSL version 1.0.2a released
===
OpenSSL - The Open Source toolkit for SSL/TLS
http://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.0.2a of our open source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OpenSSL version 1.0.0r released
===
OpenSSL - The Open Source toolkit for SSL/TLS
http://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.0.0r of our open source
Hello,
I am currently out of office and will not read your email untill Monday, the
23rd of January. In urgent cases please contact managed.serv...@lcsystems.ch.
Best regards,
Isaac Hailperin
___
openssl-users mailing list
To unsubscribe:
15 matches
Mail list logo
