{"id":185,"date":"2006-01-11T06:43:11","date_gmt":"2006-01-11T14:43:11","guid":{"rendered":"http:\/\/multimedia.cx\/eggs\/?p=185"},"modified":"2006-01-11T06:48:50","modified_gmt":"2006-01-11T14:48:50","slug":"us-government-multimedia-hackers","status":"publish","type":"post","link":"https:\/\/multimedia.cx\/eggs\/us-government-multimedia-hackers\/","title":{"rendered":"U.S. Government Multimedia Hackers"},"content":{"rendered":"

xine colleague James Courtier-Dutton informs of a curious story via the xine-devel mailing list: Homeland Security helps secure open-source code<\/a>. It seems that the U.S. Department of Homeland Security wants to run code audits on a number of increasingly-used multimedia applications. On the TODO list are xine<\/a> and MPlayer<\/a>.<\/p>\n


\n\"DHS<\/a>
\n<\/center><\/p>\n

It’s weird to think the government is commissioning to improve code I helped write. But multimedia players are certainly not exempt from security bugs– one of my more humbling experiences was when a code audit made be students of D.J. Bernstein’s<\/a> security class found a careless buffer overflow condition in one of xine demuxer modules.<\/p>\n","protected":false},"excerpt":{"rendered":"

xine colleague James Courtier-Dutton informs of a curious story via the xine-devel mailing list: Homeland Security helps secure open-source code. It seems that the U.S. Department of Homeland Security wants to run code audits on a number of increasingly-used multimedia applications. On the TODO list are xine and MPlayer. It’s weird to think the government […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-185","post","type-post","status-publish","format-standard","hentry","category-open-source-multimedia"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t