1
Fork 0

new post Things I read, Week 3

This commit is contained in:
Jan-Erik Rediger 2018-01-15 20:30:38 +01:00
parent a74665ea4a
commit fe8a4d769f
2 changed files with 26 additions and 9 deletions

View file

@ -1,9 +0,0 @@
extends: post.liquid
title: "Things I read, Week 3"
date: 15 Jan 2018 12:00:00 +0100
path: /:year/:month/:day/things-i-read-week-3
route: blog
---
This post is part of a [new experiment this year](/2018/01/08/things-i-read-week-2/index.html):
Trying to briefly collect articles/posts/code/documentation I read in the past week and add some comments for things I consider important.

View file

@ -0,0 +1,26 @@
permalink: "/{{ year }}/{{ month }}/{{ day }}/things-i-read-week-3"
title: "Things I read, Week 3"
published_date: "2018-01-15 20:30:00 +0100"
layout: post.liquid
data:
route: blog
---
This post is part of a [new experiment this year](/2018/01/08/things-i-read-week-2/index.html):
Trying to briefly collect articles/posts/code/documentation I read in the past week and add some comments for things I consider important.
### Video: [DOOM - Behind the music](https://www.youtube.com/watch?v=U4FNBMZsqrY)
> Change the process, change the outcome
Not so much _read_, but watched.
A super entertaining talk by [Nick Gordon](https://twitter.com/Nick_Gordon) explaining the process of the making of the DOOM soundtrack.
I have no idea about audio engineering or musical creativity, but I still enjoyed this talk a lot.
### Paper: [Meltdown](https://meltdownattack.com/meltdown.pdf)
One half of the recent [CPU Exploitation desaster](https://meltdownattack.com/).
The paper is not even that complex and in a scientific way keeps repeating itself.
It clearly lays out the simple instruction sequence that's necessary to trigger the exploitable behaviour.
Quite a nice addition to the [explanations by Google's Project Zero](https://googleprojectzero.blogspot.de/2018/01/reading-privileged-memory-with-side.html).