Feed digilinux.ru [copy] http://digilinux.ru/feed/ has loading error: cURL error 22: The requested URL returned error: 403 Forbidden
Feed freepost [copy] https://freepo.st/rss/new has loading error: cURL error 6: Could not resolve host: freepo.st
How DOOM fire was made
How the playstation and Nintendo 64 version of DOOM implemented fire.
Deciphering the postcard sized raytracer
How Andrew Kensler did it again and authored a breathtaking path tracer fitting on a postcard.
How the Dreamcast copy protection was defeated
How the Dreamcast copy protection was defeated!
Game Engine Black Book: Wolfenstein 3D, 2nd Edition
The second edition of the Game Engine Black Book: Wolfenstein 3D is out.
ToxCon 2018 report
This year’s ToxCon was super fun, thanks to everyone who attended it!
If you have missed the event, list of talks, talk slides and some photos from the event are available online. No videos are available as it was decided not to record the talks.
We are planning to hold another ToxCon the next year, so keep an eye for announcements. If you are working on anything fun with Tox and want to share it with the world, consider giving a talk at the next ToxCon — we would be happy to host your talk.
Here are a couple of the photos from...
Memory leak bug and new Toxcore release fixing it
A memory leak bug was discovered in Toxcore that can be triggered remotely to exhaust one’s system memory, resulting in a denial of service attack. The bug is present in the TCP Server module of Toxcore and therefore it affects mostly bootstrap nodes. Regular Tox clients generally have the TCP Server functionality disabled by default, leaving them unaffected.
The bug was introduced on July 15th, 2014 in commit 22d28ddf36563e2d0018fc20cafdfe61278dd67f, making all previous versions of TokTok c-toxcore and irungentoo’s toxcore vulnerable.
The bug is fixed in TokTok c-toxcore v0.2.8. The bug is also fixed in the master branch of irungentoo’s toxcore, in commit...