Files
ioccc/2015/endoh2
Cody Boone Ferguson 4bf3f302cb 'comments' -> 'remarks' in all README.md files
As in

    sgit -e 's/\([Aa]uthor.*\)comments/\1remarks/g' -e 's/\([Jj]udge.*\)comments/\1remarks/g' '*README.md'
2023-04-10 11:01:39 -07:00
..
2020-12-30 16:57:03 -08:00

Most Overlooked Obfuscation

Yusuke Endoh  
<https://github.com/mame/>  
Twitter: @mametter  

To build:

make

To run:

./prog

Try:

cat prog.c

./prog | diff - prog.c

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 Freakin' Screen (polite form)

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

Author's remarks:

Follow this instruction 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.

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

This file is Copyright (c) 2023 by Landon Curt Noll. All Rights Reserved. You are free to share and adapt this file under the terms of this license:

Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)

For more information, see: https://creativecommons.org/licenses/by-sa/4.0/