<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/lib/libc/hidden/sha2.h, branch jd/queueboosts</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/lib/libc/hidden/sha2.h?h=jd%2Fqueueboosts</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/lib/libc/hidden/sha2.h?h=jd%2Fqueueboosts'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2016-09-03T16:25:03Z</updated>
<entry>
<title>Add functions for SHA512/256. The standard says you're supposed to start</title>
<updated>2016-09-03T16:25:03Z</updated>
<author>
<name>tedu</name>
<email>tedu@openbsd.org</email>
</author>
<published>2016-09-03T16:25:03Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=4baad0396b2cf44e7f6a7ef5bfdde5aa5100ec59'/>
<id>urn:sha1:4baad0396b2cf44e7f6a7ef5bfdde5aa5100ec59</id>
<content type='text'>
with different magic numbers, so we need to add some functions instead
of just asking the user to truncate as desired. Sigh.
SHA512 is quite a bit faster than SHA256 on 64 bit CPUs,
but 256 bit hashes are usually quite sufficient. Best of both.
ok deraadt tom
</content>
</entry>
<entry>
<title>Wrap blowfish, sha*, md5, and rmd160 so that internal calls go direct</title>
<updated>2015-09-11T09:18:27Z</updated>
<author>
<name>guenther</name>
<email>guenther@openbsd.org</email>
</author>
<published>2015-09-11T09:18:27Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=89db3a204d87a918319b4ef97bce4540c64a667e'/>
<id>urn:sha1:89db3a204d87a918319b4ef97bce4540c64a667e</id>
<content type='text'>
ok deraadt@
</content>
</entry>
</feed>
