<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/lib/libcrypto/arc4random/arc4random_netbsd.h, branch OPENBSD_7_9</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2016-06-30T12:19:51+00:00</updated>
<entry>
<title>Tighten behavior of _rs_allocate failure for portable arc4random implementations.</title>
<updated>2016-06-30T12:19:51+00:00</updated>
<author>
<name>bcook</name>
<email></email>
</author>
<published>2016-06-30T12:19:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=feaba99148498e3901e21567eef6244222c71431'/>
<id>urn:sha1:feaba99148498e3901e21567eef6244222c71431</id>
<content type='text'>
In the event of a failure in _rs_allocate for rsx, we still have a reference to
freed memory for rs on return. Not a huge deal since we subsequently abort in
_rs_init, but it looks strange on its own.

ok deraadt@
</content>
</entry>
<entry>
<title>unify files further</title>
<updated>2015-09-11T11:52:55+00:00</updated>
<author>
<name>deraadt</name>
<email></email>
</author>
<published>2015-09-11T11:52:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=2a8f39dde4eb3fc8b492e8c665128c557ff500af'/>
<id>urn:sha1:2a8f39dde4eb3fc8b492e8c665128c557ff500af</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add arc4random/getentropy shims for NetBSD.</title>
<updated>2015-01-19T20:21:40+00:00</updated>
<author>
<name>bcook</name>
<email></email>
</author>
<published>2015-01-19T20:21:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=8da41a08c1b0ad547a78765a94025ba2a25b5fb0'/>
<id>urn:sha1:8da41a08c1b0ad547a78765a94025ba2a25b5fb0</id>
<content type='text'>
The latest NetBSD (6.1.5) arc4random does not appear to reseed the CRNG state
after a fork, so provide an override until the fork-safe version in CVS appears
in a release.

These are the same as the FreeBSD shims.

ok deraadt@
</content>
</entry>
</feed>
