gulhe
/ untrusted-lvl15-solution.js
Last active
August 29, 2015 14:10
— forked from anonymous/untrusted-lvl15-solution.js
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /************************** | |
| * exceptionalCrossing.js * | |
| ************************** | |
| * | |
| * Sorry, old friend, but I'm afraid I can't share | |
| * co-authorship on this paper. You've done a very | |
| * good job getting this Algorithm for me. The bit | |
| * with the keys was especially clever! I wouldn't | |
| * have thought of it myself. But then, of course, | |
| * that's why you were here in the first place. |
gulhe
/ untrusted-lvl1-solution.js
Last active
August 29, 2015 14:10
— forked from anonymous/untrusted-lvl1-solution.js
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /***************** | |
| * cellBlockA.js * | |
| ***************** | |
| * | |
| * Good morning, Dr. Eval. | |
| * | |
| * It wasn't easy, but I've managed to get your computer down | |
| * to you. This system might be unfamiliar, but the underlying | |
| * code is still JavaScript. Just like we predicted. | |
| * |
gulhe
/ untrusted-lvl15-solution.js
Last active
August 29, 2015 14:10
— forked from anonymous/untrusted-lvl15-solution.js
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /************************** | |
| * exceptionalCrossing.js * | |
| ************************** | |
| * | |
| * Sorry, old friend, but I'm afraid I can't share | |
| * co-authorship on this paper. You've done a very | |
| * good job getting this Algorithm for me. The bit | |
| * with the keys was especially clever! I wouldn't | |
| * have thought of it myself. But then, of course, | |
| * that's why you were here in the first place. |
NewerOlder