Cody Boone Ferguson
009e1b7522
The location of the link is in the About menu under the 'Contacting the IOCCC' and above 'Thanks for the help'. At first I had it at the very bottom, under 'IOCCC markdown guidelines', but it seemed better to have it closer to contacting the IOCCC. This is the same location in the no JavaScript menu (which, for those who do not know or forget, is not a requirement except for some screen sizes). The top level Makefile has a new 'security' rule. Updated make help. Typo fixes in make help. SECURITY.html has had a few updates as well: change the wording of entry code is unsupported (it now says 'ALL CODE IN ALL IOCCC ENTRIES IS UNSUPPORTED!!') and it now links to the mkiocccentry repo and how to report a possible security vulnerability in that repo; as that IS supported - and since there was reference to discussing security concerns is in SECURITY.html - even though the entries will not receive security updates - it seemed a good idea to have a link to report such security issues in the mkiocccentry repo. Perhaps the FAQ needs to be updated for this too.
To build:
make
To use:
./hamano < textfile > output.pdf
Try:
./try.sh
The script will generate a number of PDF files and it will suggest you look at
them as well. You can read hint.pdf with a PDF reader like acroread hint.pdf
or evince hint.pdf. With macOS you can do open hint.pdf which by default
will open Preview.app. You may of course use your pdf viewer to open the file
directly instead.
One of the PDF files generated the README.md file as a PDF, obfuscated, and the PDF file will then be compiled as C (itself!) and executed so that it shows README.md!
That procedure looks like:
./hamano < README.md > hint.pdf
cc -xc hint.pdf -o hint
./hint
Another PDF generated is an obfuscated Hello World! program (obfuscated inside
the PDF). Once this is done it will compile the PDF as if it was C (itself!). It
will look like:
echo 'int main(){puts("Hello World!");}' | ./hamano > hello.pdf
cc -xc hello.pdf -o hello
./hello | cc -Wno-implicit-function-declaration -xc - -o ./hello2
./hello2
although the CFLAGS will be what is in the Makefile as it uses the helper
rules hint.pdf, hint, hello.pdf and hello to do this.
Judges' remarks:
This entry treads into a new territory for IOCCC - generating PDF files.
The originally submitted entry could have been thought of as a "Best abuse of Ghostscript" entry. :-)
The source code and rendered pages are obfuscated for humans (where is the font?), and the submitted entry created PDF files that left Ghostscript confused.
The results can be viewed with Acrobat Reader, evince and Apple's Preview.
The updated version can also be viewed using Ghostscript.
There is something strange about the little flags in the output. A search of English literature will provide a hint. The conclusion you might draw is too elementary. :-)
So what do those flags really mean?
The Dancing men algorithm might be useful.
Don't forget to take a look at the generated PDF. Perhaps you might even want to compile the output with a C compiler. When you run it, what does it output?
Author's remarks:
This program obfuscate text file into PDF file with Dancing men algorithm.
Probably, the output PDF file is compliant with PDF 1.3 and it's also available to compile as C code.
I've tested it with GCC 4.7 and Clang 3.0 with Linux, and the following PDF Readers:
- Adobe Acrobat Reader
- Evince
- Ghostscript
- Xpdf
Obfuscations
This program is obfuscated by using classical methods. But can you find the embedded font in the fragmented glyph?