<feed xmlns='http://www.w3.org/2005/Atom'>
<title>zears/aezref/aezv5/aesni, branch master</title>
<subtitle>AEZ v5 implementation in Rust</subtitle>
<link rel='alternate' type='text/html' href='https://git.kingdread.de/cgit.cgi/zears/'/>
<entry>
<title>fuzz against slow aez-ref, not fast aez-ni</title>
<updated>2025-04-17T10:56:44+00:00</updated>
<author>
<name>Daniel Schadt</name>
<email>kingdread@gmx.de</email>
</author>
<published>2025-04-17T10:56:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.kingdread.de/cgit.cgi/zears/commit/?id=9287a6cdc37c7c37e744f8418a13a74bb0e629ef'/>
<id>9287a6cdc37c7c37e744f8418a13a74bb0e629ef</id>
<content type='text'>
Two reasons:

First, this allows us to test more of the algorithm, as the (slow)
reference implementation supports multiple associated data items, large
values for tau, ...

Second, this avoids the segfault crash, which is a limit of the fast
implementation (the assumption there is that data is aligned properly,
and even a read out-of-bounds will not cause a segfault).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Two reasons:

First, this allows us to test more of the algorithm, as the (slow)
reference implementation supports multiple associated data items, large
values for tau, ...

Second, this avoids the segfault crash, which is a limit of the fast
implementation (the assumption there is that data is aligned properly,
and even a read out-of-bounds will not cause a segfault).
</pre>
</div>
</content>
</entry>
</feed>
