A simultaneous OS X binary, PDF file, jar file, and HTML page
mix.corkami.com
mix.corkami.com
They serve no purpose, except proving that file formats not starting at offset
0 are a bad idea.
Au contraire–they are a wonderful idea. If, say, a polyglot pdf+executable could gain code execution enough to execute itself as a binary, it could just as easily execute far more dangerous code while being far less likely to tip off an automated scanner. So it goes for many of the other stackable formats.The benefits seem to far outweigh the drawbacks. As an example, look at the concept behind ext[234]fs migration in btrfs (which is not fixed to block 0 in a volume)–Take an ext4 filesystem, generate new inodes pointing at the original b-trees, and away you go! You get a filesystem that is valid ext4 (retaining the old data), and valid btrfs (which, being copy-on-write, doesn't destroy the old data.)
Meanwhile, we realy need to develop network protocols with obfuscated handshake to counter monitor and censorship.
I recommend also checking my latest slides @ https://corkami.googlecode.com/files/44CON2013-Messing%20wit... where the 'inception' slides contain the PDF slides and the actual PDF viewer Sumatra, and an alternate PDF to be viewed under Chrome ;)
[1] - http://www.44con.com/
I have only one fez.
I though you were the Fez variant of Cookie monster minus the eating of Fezzes?
reference: http://www.youtube.com/watch?v=bvWYw0CnuSI
http://stackoverflow.com/a/2083161/41948
Now someone could just add Mach-O to it...
PE, ELF, and Mach-O all enforce a different signature at offset 0. Thus it's impossible to combine them - otherwise, I'd have done it already ;)
I tried .vbs+.bat hybrid and .bat+.com hybrid.
http://demoseen.com/windowpane/magister.png.html
(I'm not the creator, I just happen to share an IRC channel with them.) There is a description of how it works at http://daeken.com/superpacking-js-demos