Timeline for Is H.264 subject to exploits / are some H.264 codecs subject to exploits?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 14, 2015 at 18:41 | history | edited | Peter Cordes | CC BY-SA 3.0 |
run in a sandbox
|
| Mar 14, 2015 at 18:36 | comment | added | Peter Cordes | Probably no better than MP4->MP4 remuxing. MP4->MKV MIGHT turn a buffer overflow -> remote code execution into just a crash in chapter parsing code, for example. (Or it might not, remuxing won't always help.) Putting it back into MP4 might line things up the same way as the original container. If you really still want the output to be MP4, mp4->mp4 remux is probably the same as mp4->mkv->mp4. And you could do it with MP4Box or something, instead of ffmpeg. | |
| Mar 7, 2015 at 23:28 | comment | added | Mark Gerolimatos | Thank you for the excellent answer! So if I were looking to sanitize the container, an MP4->MKV->MP4 would be superior to a straight MP4->MP4 recontainerization? | |
| Mar 7, 2015 at 23:26 | vote | accept | Mark Gerolimatos | ||
| Mar 7, 2015 at 22:14 | history | answered | Peter Cordes | CC BY-SA 3.0 |