<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openssl, branch OpenSSL_1_1_0f</title>
<subtitle>TLS/SSL and crypto library.</subtitle>
<id>http://git.bktus.com/gpgfrontend/openssl/atom?h=OpenSSL_1_1_0f</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/openssl/atom?h=OpenSSL_1_1_0f'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/'/>
<updated>2017-05-25T12:46:16Z</updated>
<entry>
<title>Prepare for 1.1.0f release</title>
<updated>2017-05-25T12:46:16Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2017-05-25T12:46:16Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=577d7010c6ffa98e8dc61d8826693db9d8f57bd5'/>
<id>urn:sha1:577d7010c6ffa98e8dc61d8826693db9d8f57bd5</id>
<content type='text'>
Reviewed-by: Stephen Henson &lt;steve@openssl.org&gt;
</content>
</entry>
<entry>
<title>Update CHANGES and NEWS for new release</title>
<updated>2017-05-25T11:43:08Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2017-05-25T09:54:19Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=058253ada225c01e1a87ec6cb063627b9295ac37'/>
<id>urn:sha1:058253ada225c01e1a87ec6cb063627b9295ac37</id>
<content type='text'>
Reviewed-by: Kurt Roeckx &lt;kurt@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/3547)</content>
</entry>
<entry>
<title>Document that PKCS#12 functions assume UTF-8 for passwords</title>
<updated>2017-05-24T20:17:27Z</updated>
<author>
<name>David Woodhouse</name>
<email>dwmw2@infradead.org</email>
</author>
<published>2017-05-24T11:18:14Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=df73fcdc1bfab4125d8e79d4a0b6e9c2c2e85787'/>
<id>urn:sha1:df73fcdc1bfab4125d8e79d4a0b6e9c2c2e85787</id>
<content type='text'>
Part of issue #3531

Reviewed-by: Rich Salz &lt;rsalz@openssl.org&gt;
Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/3535)
(cherry picked from commit cff85f39e438830cb5bc8bf7cb2ed6458670c5be)
</content>
</entry>
<entry>
<title>Clarify what character encoding is used in the returned UI strings</title>
<updated>2017-05-24T20:14:55Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2017-05-23T17:52:54Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=b024891f7f84d657d1c9b1f0d364dc1c3c42f411'/>
<id>urn:sha1:b024891f7f84d657d1c9b1f0d364dc1c3c42f411</id>
<content type='text'>
Reviewed-by: Rich Salz &lt;rsalz@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/3532)
(cherry picked from commit 789d6dddecbc231f5c858d203aab318cf81676fd)
</content>
</entry>
<entry>
<title>Fix typo in doc/man3/EVP_EncrypInit.pod</title>
<updated>2017-05-23T08:31:59Z</updated>
<author>
<name>Paul Yang</name>
<email>paulyang.inf@gmail.com</email>
</author>
<published>2017-05-22T15:18:45Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=e242656cb1184a713911dd53206799bda02fe15b'/>
<id>urn:sha1:e242656cb1184a713911dd53206799bda02fe15b</id>
<content type='text'>
In the example section.

CLA: trivial

Signed-off-by: Paul Yang &lt;paulyang.inf@gmail.com&gt;

Reviewed-by: Rich Salz &lt;rsalz@openssl.org&gt;
Reviewed-by: Matt Caswell &lt;matt@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/3520)
(cherry picked from commit 719b289d62d32fe45226e8bc5b4fb0d76f6a1b5d)
</content>
</entry>
<entry>
<title>[1.1.0 backport] set entry type on SCTs from X.509 and OCSP extensions</title>
<updated>2017-05-22T16:44:26Z</updated>
<author>
<name>Alex Gaynor</name>
<email>alex.gaynor@gmail.com</email>
</author>
<published>2017-05-22T13:37:57Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=51ab051ba62a1ceabb2724d69b2d4c954c697f89'/>
<id>urn:sha1:51ab051ba62a1ceabb2724d69b2d4c954c697f89</id>
<content type='text'>
Reviewed-by: Matt Caswell &lt;matt@openssl.org&gt;
Reviewed-by: Rich Salz &lt;rsalz@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/3519)</content>
</entry>
<entry>
<title>Fix infinite loops in secure memory allocation.</title>
<updated>2017-05-22T12:48:21Z</updated>
<author>
<name>Todd Short</name>
<email>tshort@akamai.com</email>
</author>
<published>2017-05-11T19:48:10Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=ddcccb65185cdf51b17433ad2a63abc7fedb1e2e'/>
<id>urn:sha1:ddcccb65185cdf51b17433ad2a63abc7fedb1e2e</id>
<content type='text'>
Remove assertion when mmap() fails.
Only give the 1&lt;&lt;31 limit test as an example.

Fix the small arena test to just check for the symptom of the infinite
loop (i.e. initialized set on failure), rather than the actual infinite
loop. This avoids some valgrind errors.

Backport of:
PR #3512 commit fee423bb68869de02fceaceefbc847e98213574b
PR #3510 commit a486561b691d6293a901b412172ca0c6d1ffc0dc
PR #3455 commit c8e89d58a5d44b9dd657d6d13a5a10d1d4d30733
PR #3449 commit 7031ddac94d0ae616d1b0670263a9265ce672cd2

Issue 1:

sh.bittable_size is a size_t but i is and int, which can result in
freelist == -1 if sh.bittable_size exceeds an int.

This seems to result in an OPENSSL_assert due to invalid allocation
size, so maybe that is "ok."

Worse, if sh.bittable_size is exactly 1&lt;&lt;31, then this becomes an
infinite loop (because 1&lt;&lt;31 is a negative int, so it can be shifted
right forever and sticks at -1).

Issue 2:

CRYPTO_secure_malloc_init() sets secure_mem_initialized=1 even when
sh_init() returns 0.

If sh_init() fails, we end up with secure_mem_initialized=1 but
sh.minsize=0. If you then call secure_malloc(), which then calls,
sh_malloc(), this then enters an infite loop since 0 &lt;&lt; anything will
never be larger than size.

Issue 3:

That same sh_malloc loop will loop forever for a size greater
than size_t/2 because i will proceed (assuming sh.minsize=16):
i=16, 32, 64, ..., size_t/8, size_t/4, size_t/2, 0, 0, 0, 0, ....
This sequence will never be larger than "size".

Reviewed-by: Andy Polyakov &lt;appro@openssl.org&gt;
Reviewed-by: Rich Salz &lt;rsalz@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/3453)</content>
</entry>
<entry>
<title>Fix srp app missing NULL termination with password callback</title>
<updated>2017-05-22T08:30:44Z</updated>
<author>
<name>Diego Santa Cruz</name>
<email>Diego.SantaCruz@spinetix.com</email>
</author>
<published>2017-05-16T14:05:19Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=0870b2cdaa65a30645bd0cc70f7ad6e30db7a2cf'/>
<id>urn:sha1:0870b2cdaa65a30645bd0cc70f7ad6e30db7a2cf</id>
<content type='text'>
The password_callback() function does not necessarily NULL terminate
the password buffer, the caller must use the returned length but the
srp app uses this function as if it was doing NULL termination.

This made the -passin and -passout options of "openssl srp"
fail inexpicably and randomly or even crash.

Fixed by enlarging the buffer by one, so that the maximum password length
remains unchanged, and adding NULL termination upon return.

[Rearrange code for coding style compliance in process.]

Reviewed-by: Matt Caswell &lt;matt@openssl.org&gt;
Reviewed-by: Andy Polyakov &lt;appro@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/3475)

(cherry picked from commit 0e83981d61fc435f42d4bb4d774272b69556b7bc)
</content>
</entry>
<entry>
<title>test/run_tests.pl: don't mask test failures.</title>
<updated>2017-05-22T08:18:15Z</updated>
<author>
<name>Andy Polyakov</name>
<email>appro@openssl.org</email>
</author>
<published>2017-05-21T09:40:46Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=c7f6ec9e5afc575df260c21ba77cf3a45a8b9b39'/>
<id>urn:sha1:c7f6ec9e5afc575df260c21ba77cf3a45a8b9b39</id>
<content type='text'>
Switch to TAP::Harness inadvertently masked test failures.
Test::Harness::runtests was terminating with non-zero exit code in case
of failure[s], while TAP::Harness apparently holds caller responsible
for doing so.

Reviewed-by: Rich Salz &lt;rsalz@openssl.org&gt;
Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
</content>
</entry>
<entry>
<title>-inkey can be an identifier, not just a file</title>
<updated>2017-05-21T22:24:49Z</updated>
<author>
<name>Rich Salz</name>
<email>rsalz@openssl.org</email>
</author>
<published>2017-05-21T01:44:31Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=8f59b3267ddbffc6dd0da780fe5a1f3dcc4a2259'/>
<id>urn:sha1:8f59b3267ddbffc6dd0da780fe5a1f3dcc4a2259</id>
<content type='text'>
update pkcs12, smime, ts apps.

Reviewed-by: Tim Hudson &lt;tjh@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/3507)
(cherry picked from commit 48b5352212d8c68f7fd071ca9f38822b7e954c5a)
</content>
</entry>
</feed>
