fixed shebangs

[hidehiroanto]

changed all python shebangs from #!/opt/pwn.college/python to #!/usr/bin/exec-suid -- /usr/bin/python3 -I

[hidehiroanto]

also deleted the file mentioned in #56, it's the only one I found

[zardus]

I have good news and bad news.

The bad news is that the vast majority of these challenges are generated from templates, so this fix, while temporarily effective, won't hold long-term. The further bad news is that the templated challenges are an unmaintainable disaster and, even worse, that we have no way to share them without also sharing the embedded solutions. This last part isn't quite a problem for you (happy to give you access to the templates), but is a problem for the general case of people contributing to challenges.

The good news is that we're trying to improve the situation. Here is one attempt: https://github.com/pwncollege/challenges . As you can see, I have two challenges ported, but hopefully things will speed up if we decide to go this route. Would love to have your help if you're interested :-)

In the long-run, if we go with that direction, we're hoping to have literally all the core pwn.college curriculum living there, easily deployable, PRable, and CIable. Then we'll add edit buttons on the challenges themselves, and achieve Connor's vision of being the Wikipedia of hacking education!

[hidehiroanto]

This is mostly an emergency fix since not moving to exec-suid ASAP for web security introduces very big problems

I also noticed that the intercepting communications exec-suid shebang uses /usr/local/bin/python now instead of /usr/bin/python3 (df555fb) due to using a different base image than challenge-legacy, should that be standard from now on?

[zardus]

Okay, it's yolo time.

The /usr/local/bin/python3 will be resolved by pwncollege/challenge-images#6