<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mike/sst/src/3p/monocypher, branch v0.9-BETA</title>
<subtitle>Source Speedrun Tools: practice tools and handy features for Source Engine games</subtitle>
<id>https://git.woz.blue/mike/sst/atom?h=v0.9-BETA</id>
<link rel='self' href='https://git.woz.blue/mike/sst/atom?h=v0.9-BETA'/>
<link rel='alternate' type='text/html' href='https://git.woz.blue/mike/sst/'/>
<updated>2023-06-21T23:06:39+00:00</updated>
<entry>
<title>Update Monocypher yet again, to 4.0.1</title>
<updated>2023-06-21T23:06:39+00:00</updated>
<author>
<name>Michael Smith</name>
<email>mikesmiffy128@gmail.com</email>
</author>
<published>2023-06-21T23:06:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.woz.blue/mike/sst/commit/?id=f2471014aae74c089eda1461a740001d77c233f2'/>
<id>urn:sha1:f2471014aae74c089eda1461a740001d77c233f2</id>
<content type='text'>
There's a solid chance this actually gets used this time. Plus, there's
breaking changes, so it makes sense to update before writing any actual
code for it.

The RNG module is also manually fixed up; upstream wasn't moved to the
new Monocypher APIs which might be because the authors don't seem to
think it's even a good idea to use anything other than arc4random().
Maybe I'd kind of agree with that if not for both Linux and Windows not
having arc4random(), and none of SSTs use cases requiring it either
(none of the crypto code is gonna be multithreaded and certainly none of
it is gonna fork).
</content>
</entry>
<entry>
<title>Import Monocypher 3.1.3 + monocypher-rng module</title>
<updated>2022-08-16T21:52:47+00:00</updated>
<author>
<name>Michael Smith</name>
<email>mikesmiffy128@gmail.com</email>
</author>
<published>2022-07-31T15:01:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.woz.blue/mike/sst/commit/?id=9f12b8d3a30fc9137d6707dcc513de30022ffe3e'/>
<id>urn:sha1:9f12b8d3a30fc9137d6707dcc513de30022ffe3e</id>
<content type='text'>
This is for somewhat later. I'd always planned to use it - it existed
already in earlier private repos, in fact. I just didn't bother to
import it here in case it wouldn't actually be needed, but with the way
current plans are going, it's definitely going to be needed, so here it
is.
</content>
</entry>
</feed>
