The great cracking challenge
Posted: Wed Feb 23, 2011 7:55 pm
We all know LÖVE has gaping security holes. Some people don't like that. I forked LÖVE to make a sandboxed version, mostly to inspire actual changes in the main LÖVE fork. That fork is SELÖVE.
I recently updated it to be compatible with LÖVE 0.7.1.
The thing is, I don't really know if I missed some ways of reaching outside the sandbox.
So I present to you a challenge: find a way to crack SELÖVE with a malicious .love file. If you succeed, you win one (1) free internets. Also, eternal glory.
The source, a 64-bit .deb and an slightly outdated* 32-bit Windows executable** are available on the Bitbucket downloads page, so you can test them.
* Equivalent to LÖVE 0.7.0, but sandboxing should be the same.
** Generously provided by TechnoCat.
So, who thinks they can beat this?
NOTE: This should be obvious, but any casual readers might want to note that this is not a topic where you'll want to download and run all .loves you can find. By design, they might be harmful to your computer, especially when run with vanilla LÖVE.
I recently updated it to be compatible with LÖVE 0.7.1.
The thing is, I don't really know if I missed some ways of reaching outside the sandbox.
So I present to you a challenge: find a way to crack SELÖVE with a malicious .love file. If you succeed, you win one (1) free internets. Also, eternal glory.
The source, a 64-bit .deb and an slightly outdated* 32-bit Windows executable** are available on the Bitbucket downloads page, so you can test them.
* Equivalent to LÖVE 0.7.0, but sandboxing should be the same.
** Generously provided by TechnoCat.
So, who thinks they can beat this?
NOTE: This should be obvious, but any casual readers might want to note that this is not a topic where you'll want to download and run all .loves you can find. By design, they might be harmful to your computer, especially when run with vanilla LÖVE.