Image files of some sort (JPGs, PNGs), probably not an issue.

Because, of course, we know that there are never occasions where a buffer overflow in an image processing library affects common client web browsers. That being said, I'm not sure how exactly one checks for stuff like this when the underlying libraries one wishes to use may contain unknown buffer overflows or other exploit-enabling coding errors themselves.

@/=map{[/./g]}qw/.h_nJ Xapou cets krht ele_ r_ra/;
map{y/X_/\n /;print}map{pop@$_}@/for@/
[download]