this is a surprisingly fun project. though i had to figure out how to get the atmega384p to stop glitching out when i blast it with data over serial
it’s running at 10 fps (display can’t go faster), though the buttons are updated at 20 fps. the data for both is coming from ffmpeg (display is just rawvideo with monob pixfmt, LEDs are showvolume scaled to 4x1 px)
also those buttons make a very satisfying kachunk
in any case, mitigating this application-side will be much easier once i stop being lazy and finish refactoring this piece of shit.
i want user-defined filters, not the hardcoded mess i have right now
got contacted by a security researcher about a server-side request forgery vulnerability in 0x0.
in other words, the URL fetch feature may expose local networks.
dude if address-based trust is part of your security model, you’ve got bigger problems. dealing with network topology is not an application problem. protect sensitive services with strong authentication, protect sensitive networks close to the network layer. on linux, filtering packets per uid/gid is easy enough, too.
turned out to be a mesa/radeonsi bug
i run 0x0.st
let’s be friends?