<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/lib/libcrypto/crypto/Makefile, branch libressl-v2.2.0</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=libressl-v2.2.0</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=libressl-v2.2.0'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2015-04-11T16:16:15+00:00</updated>
<entry>
<title>Send OPENSSL_issetugid() straight to hell, no final cigarette.</title>
<updated>2015-04-11T16:16:15+00:00</updated>
<author>
<name>deraadt</name>
<email></email>
</author>
<published>2015-04-11T16:16:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=01d65208fd8dd61fb0f8c5d92ff80c7630a7c2b5'/>
<id>urn:sha1:01d65208fd8dd61fb0f8c5d92ff80c7630a7c2b5</id>
<content type='text'>
The issetugid() API is supposed to make a strong promise where "0
means it is safe to look at the environment".  Way back in the past
someone on the OpenSSL team responded to the environment access danger
by creating a wrapper called OPENSSL_issetugid, and went to use it a
number of places.  However, by default on systems lacking true
issetugid(), OPENSSL_issetugid returns 0.  0 indicating safely.  False
safety.  Which means OPENSSL_issetugid() fails to make any sort of
promise about safety, in fact it is just the opposite.

Can you believe the OpenSSL team?

This nastiness was noticed over the years, however noone could gain traction
and get it fixed in OpenSSL.  Also see a paragraph about this in
http://www.tedunangst.com/flak/post/worst-common-denominator-programming

ok jsing
</content>
</entry>
<entry>
<title>unifdef OPENSSL_NO_RFC3779 - this is currently disabled and unlikely to</title>
<updated>2015-02-10T13:28:17+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2015-02-10T13:28:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=b5dcc59b2cf1dad7e9ebcc08266a1bf71c384886'/>
<id>urn:sha1:b5dcc59b2cf1dad7e9ebcc08266a1bf71c384886</id>
<content type='text'>
be enabled, mostly since people use SANs instead.

ok beck@ guenther@
</content>
</entry>
<entry>
<title>Remove RC5 code - this is not currently enabled and is not likely to ever</title>
<updated>2015-02-10T11:37:58+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2015-02-10T11:37:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=f1d598735f0b0ffb1d0c0a4960577043026a928e'/>
<id>urn:sha1:f1d598735f0b0ffb1d0c0a4960577043026a928e</id>
<content type='text'>
be enabled.

Removes one symbol from libcrypto, however there is no ABI change.

ok beck@ miod@ tedu@
</content>
</entry>
<entry>
<title>Remove crypto/store - part of which is "currently highly experimental".</title>
<updated>2015-02-10T11:16:33+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2015-02-10T11:16:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=cdb7be83319e074737e0c8a1a62fed485bd1c0de'/>
<id>urn:sha1:cdb7be83319e074737e0c8a1a62fed485bd1c0de</id>
<content type='text'>
This code is not compiled in and OPENSSL_NO_STORE is already defined in
opensslfeatures.h. No symbol removal for libcrypto.

ok beck@
</content>
</entry>
<entry>
<title>Combine c_allc.c and c_alld.c into c_all.c - there is not much point having</title>
<updated>2015-02-07T03:23:05+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2015-02-07T03:23:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=6389a5eaca6608f6d86d874f1ec6b5155822b208'/>
<id>urn:sha1:6389a5eaca6608f6d86d874f1ec6b5155822b208</id>
<content type='text'>
this split across files, especially when two of them have less code than
license text.

ok bcook@ beck@ doug@ miod@
</content>
</entry>
<entry>
<title>Add X509_STORE_load_mem() to load certificates from a memory buffer</title>
<updated>2015-01-22T09:06:39+00:00</updated>
<author>
<name>reyk</name>
<email></email>
</author>
<published>2015-01-22T09:06:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=862d0b8723d1dd780e301615518a21818f474a9c'/>
<id>urn:sha1:862d0b8723d1dd780e301615518a21818f474a9c</id>
<content type='text'>
instead of disk.  OpenSSL didn't provide a built-in API from loading
certificates in a chroot'ed process that doesn't have direct access to
the files.  X509_STORE_load_mem() provides a new backend that will be
used by libssl and libtls to implement such privsep-friendly
functionality.

Adopted for LibreSSL based on older code from relayd (by pyr@ and myself)
With feedback and OK bluhm@
</content>
</entry>
<entry>
<title>Move Windows OS-specific functions to make porting easier.</title>
<updated>2014-12-03T22:14:38+00:00</updated>
<author>
<name>bcook</name>
<email></email>
</author>
<published>2014-12-03T22:14:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=dce88910ead3a43bc663d7d9e46e2689189ac19d'/>
<id>urn:sha1:dce88910ead3a43bc663d7d9e46e2689189ac19d</id>
<content type='text'>
Several functions that need to be redefined for a Windows port are right
in the middle of other code that is relatively portable. This patch
isolates the functions that need Windows-specific implementations so
they can be built conditionally in the portable tree.

ok jsing@ deraadt@
</content>
</entry>
<entry>
<title>Oops, make sure camellia is compiled on platforms without an arch-specific</title>
<updated>2014-11-20T19:19:09+00:00</updated>
<author>
<name>miod</name>
<email></email>
</author>
<published>2014-11-20T19:19:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=0756f4d6600a6a1bc7ea507aea3d13f405a4a3af'/>
<id>urn:sha1:0756f4d6600a6a1bc7ea507aea3d13f405a4a3af</id>
<content type='text'>
Makefile.inc (i.e. landisk and m88k)
</content>
</entry>
<entry>
<title>Enable the build of GOST routines in libcrypto. Riding upon the Cammelia</title>
<updated>2014-11-18T05:31:47+00:00</updated>
<author>
<name>miod</name>
<email></email>
</author>
<published>2014-11-18T05:31:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=0690f68b8ace3f1616822e1b9dbf5656beaaea16'/>
<id>urn:sha1:0690f68b8ace3f1616822e1b9dbf5656beaaea16</id>
<content type='text'>
libcrypto minor bump.
</content>
</entry>
<entry>
<title>Add the Cammelia cipher to libcrypto.</title>
<updated>2014-11-17T20:31:22+00:00</updated>
<author>
<name>miod</name>
<email></email>
</author>
<published>2014-11-17T20:31:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=1327462df8cb4ae2dc056e0de53b4b4dc50f50fa'/>
<id>urn:sha1:1327462df8cb4ae2dc056e0de53b4b4dc50f50fa</id>
<content type='text'>
There used to be a strong reluctance to provide this cipher in LibreSSL in the
past, because the licence terms under which Cammelia was released by NTT were
free-but-not-in-the-corners, by restricting the right to modify the source
code, as well retaining the right to enforce their patents against anyone
in the future.

However, as stated in http://www.ntt.co.jp/news/news06e/0604/060413a.html ,
NTT changed its mind and made this code truly free. We only wish there had
been more visibility of this, for we could have had enabled Cammelia
earlier (-:

Licence change noticed by deraadt@. General agreement from the usual LibreSSL
suspects.

Crank libcrypto.so minor version due to the added symbols.
</content>
</entry>
</feed>
