<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sys/crypto/siphash.c, branch jd/simplify-queueing</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sys/crypto/siphash.c?h=jd%2Fsimplify-queueing</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sys/crypto/siphash.c?h=jd%2Fsimplify-queueing'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2018-01-05T19:05:09Z</updated>
<entry>
<title>Sync with the code in libc</title>
<updated>2018-01-05T19:05:09Z</updated>
<author>
<name>mikeb</name>
<email>mikeb@openbsd.org</email>
</author>
<published>2018-01-05T19:05:09Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=f620fa076e23562ed1d435e0a6d20a2ba857f9de'/>
<id>urn:sha1:f620fa076e23562ed1d435e0a6d20a2ba857f9de</id>
<content type='text'>
OK millert; original commit message by tedu@:

memcpy from the right place. at this point, the used variable is not
relevant. from Mark Karpilovskij.
ok millert
</content>
</entry>
<entry>
<title>The kernel has to slightly different version of SipHash_Final but with</title>
<updated>2017-04-12T18:35:50Z</updated>
<author>
<name>florian</name>
<email>florian@openbsd.org</email>
</author>
<published>2017-04-12T18:35:50Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=4ed9de9b27c39777b5b514b84bf7ea382d9288ce'/>
<id>urn:sha1:4ed9de9b27c39777b5b514b84bf7ea382d9288ce</id>
<content type='text'>
the same bug as just fixed in userland:

----------
SipHash_Final() was assuming the digest was 64-bit aligned, resulting in
misaligned memory accesses with armv7 ramdisk -Os bsd.rd ping
ok florian millert
----------

OK deraadt@
</content>
</entry>
<entry>
<title>Use standard spelling for types, and rename local variable from "free".</title>
<updated>2015-02-20T11:51:03Z</updated>
<author>
<name>tedu</name>
<email>tedu@openbsd.org</email>
</author>
<published>2015-02-20T11:51:03Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=b8a0470688ccdd7ea69464e85fa4016e7795d244'/>
<id>urn:sha1:b8a0470688ccdd7ea69464e85fa4016e7795d244</id>
<content type='text'>
No actual change, but makes it easier to reuse the code elsewhere.
Suggested by Andre Smagin
</content>
</entry>
<entry>
<title>keep this in sync a bit with userland by putting static on functions</title>
<updated>2015-02-07T05:45:06Z</updated>
<author>
<name>dlg</name>
<email>dlg@openbsd.org</email>
</author>
<published>2015-02-07T05:45:06Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=4682b2eb22fbedba91c3be00ed9fae8a08f6a51f'/>
<id>urn:sha1:4682b2eb22fbedba91c3be00ed9fae8a08f6a51f</id>
<content type='text'>
that are only used in this file.

tedu argues if something sucks we would fault before we can get to
these, and they dont do anything except maths. these symbols dont
need to be visible to ddb.

originally from Fritjof Bornebusch
suggested by and ok tedu@
</content>
</entry>
<entry>
<title>introduce SipHash, designed by Jean-Phillippe Aumasson and Daniel</title>
<updated>2014-11-04T03:01:14Z</updated>
<author>
<name>dlg</name>
<email>dlg@openbsd.org</email>
</author>
<published>2014-11-04T03:01:14Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=e07278f2960295f523e937cc246eb380ca80de0a'/>
<id>urn:sha1:e07278f2960295f523e937cc246eb380ca80de0a</id>
<content type='text'>
J. Bernstein, as described at https://131002.net/siphash/, and via
Andre Oppermanns implementation in FreeBSD.

this is supposed to be a good but cheap hash for use in places where
you want to protect against hash bucket flooding attacks.

yasuoka@ pointed me at this after i asked about possibilities for
protecting the in_pcb hash he was tinkering with.

naddy@ mikeb@ claudio@ and djm@ agree it is much better than doing nothing
commit deraadt@
</content>
</entry>
</feed>
