Remote code execution vulnerability in ImageMagick
So, we get it. Complicated file and network formats, handled in C code leads to these types of security issues.We are told that Rust will save us. Glib answer - if it was going to, it already would have (and this is from someone already writing Rust code).I hope it will lead to a change on two fronts:1. Simpler formats for file representation and data interchange. When someone tries to add an extra bitfield option, say no. When they keep trying, get a wooden stick with "no" written on it. Part of the disease of modern computing is bloated specs.2. Restrictive not permissive code bases. Exit and bail out early. Tell the user "file corrupted". Push back.