<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/lib/libcrypto/arch/hppa64, branch libressl-v2.2.4</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=libressl-v2.2.4</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=libressl-v2.2.4'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2015-06-19T06:05:11+00:00</updated>
<entry>
<title>Disable ENGINE_load_dynamic (dynamic engine support).</title>
<updated>2015-06-19T06:05:11+00:00</updated>
<author>
<name>bcook</name>
<email></email>
</author>
<published>2015-06-19T06:05:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=1ef7c35782edea8e65610a2d9d6d6d08ea90983c'/>
<id>urn:sha1:1ef7c35782edea8e65610a2d9d6d6d08ea90983c</id>
<content type='text'>
We do not build, test or ship any dynamic engines, so we can remove the dynamic
engine loader as well. This leaves a stub initialization function in its place.

ok beck@, reyk@, miod@
</content>
</entry>
<entry>
<title>i'm a dumbdumb. fix build.</title>
<updated>2014-07-11T14:33:00+00:00</updated>
<author>
<name>tedu</name>
<email></email>
</author>
<published>2014-07-11T14:33:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=856e3c4778b5006e84604d9f68cc15047c265aa4'/>
<id>urn:sha1:856e3c4778b5006e84604d9f68cc15047c265aa4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>move all the feature settings to a common header.</title>
<updated>2014-07-11T14:01:38+00:00</updated>
<author>
<name>tedu</name>
<email></email>
</author>
<published>2014-07-11T14:01:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=1c92e50863c312a71d4b1f75553972fc03dc100c'/>
<id>urn:sha1:1c92e50863c312a71d4b1f75553972fc03dc100c</id>
<content type='text'>
probably ok beck jsing miod
</content>
</entry>
<entry>
<title>Make sure we leave OPENSSL_NO_PSK in the conf files so things</title>
<updated>2014-07-11T11:41:25+00:00</updated>
<author>
<name>beck</name>
<email></email>
</author>
<published>2014-07-11T11:41:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=11b612b7d17330a0d0e95c378b6d869396b26ac5'/>
<id>urn:sha1:11b612b7d17330a0d0e95c378b6d869396b26ac5</id>
<content type='text'>
can know...
ok jsing@
</content>
</entry>
<entry>
<title>first round of static config. ok miod</title>
<updated>2014-04-18T18:08:37+00:00</updated>
<author>
<name>tedu</name>
<email></email>
</author>
<published>2014-04-18T18:08:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=9a982e5998dced39c9346c172e1650dc2323cb6c'/>
<id>urn:sha1:9a982e5998dced39c9346c172e1650dc2323cb6c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>The more you remove Chtulhu^WVMS tentacles, the more there are</title>
<updated>2014-04-15T21:17:15+00:00</updated>
<author>
<name>miod</name>
<email></email>
</author>
<published>2014-04-15T21:17:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=56a6aae6735f66fa8fcf6764997265da5e734ad3'/>
<id>urn:sha1:56a6aae6735f66fa8fcf6764997265da5e734ad3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Move build machinery for libcrypto from libssl/crypto to libcrypto, as well</title>
<updated>2014-04-11T22:51:54+00:00</updated>
<author>
<name>miod</name>
<email></email>
</author>
<published>2014-04-11T22:51:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=4362780bc2f199c11d5612e83851f6fc88139d21'/>
<id>urn:sha1:4362780bc2f199c11d5612e83851f6fc88139d21</id>
<content type='text'>
as configuration files; split manpages and .pc files between libcrypto and
libssl.
No functional change, only there to make engineering easier, and libcrypto
sources are still found in libssl/src/crypto at the moment.

ok reyk@, also discussed with deraadt@ beck@ and the usual crypto suspects.
</content>
</entry>
</feed>
