Author:

• Name: Yusuke Endoh
  Location: JP - Japan

To build:

    make

To use:

    ./prog

Try:

    ./try.sh

Judges’ remarks:

At this point you might be wondering, WTF?*

• What The Freak (polite form)

• What’s This For? (you may be wondering)

• What the Fish (python form)

How is this code obfuscated? Well look again:

    less prog.c

    more prog.c

Where did those underscores come from? Well RTFS!**

** Read the Freaking Source (polite form) ** Read The Freaking Screen (polite form)

If you are still puzzled, look at prog.c with your favorite text editor.

Author’s remarks:

Follow these instructions literally!

    cat prog.c
    gcc -w -o prog prog.c
    ./prog

You will do a double take.

Hint 1: Do less prog.c. You will see an emphasized string if your terminal supports bold.

Hint 2: Do wc -c prog.c. This is very long one-liner.

Hint 3: Open the source with an editor like vim or emacs.

Primary files

• prog.c - entry source code
• Makefile - entry Makefile
• prog.orig.c - original source code
• try.sh - script to try entry

Secondary files

• 2015_endoh2.tar.bz2 - download entry tarball
• README.md - markdown source for this web page
• .entry.json - entry summary and manifest in JSON
• .gitignore - list of files that should not be committed under git
• .path - directory path from top level directory
• index.html - this web page

Jump to: top