Complete Lack of Viral Capability

[Luiji]

Something that could make this project very popular is to remove the ability for viruses to infect systems. This means stuff such as:
- Removing the Lua I/O functions and forcing programs to use the safer love.filesystem module.
- Preventing the ability to start external processes (so that it won't extract an executable and run it).
- Preventing "require" from being used and going back to the love.filesystem.require system to prevent the library from requiring files outside of the percieved safe paths (the game directory and the configuration directory).

[pygy]

...
- Preventing "require" from being used and going back to the love.filesystem.require system to prevent the library from requiring files outside of the percieved safe paths (the game directory and the configuration directory).

No need to write a custom require function.This point could be handled by enabling/disabling the right loaders in package.loaders. Basically, scrap the table when LÖVE starts (to ditch all file.io based loaders), and replace it with one containing these three loaders:

- The current PhysFS-based one written in C++, mostly for files in the user folder (unless the next one can be adapted for that too).
- I've posted a loader based on love.filesystem.load() that should work for pure lua files and modules/submodules inside the .love file. Edit, actually, I just noticed you were the one who had posted an answer in that topic... :p

These should cover all Lua files no matter where they are located.

- To be written: A PhysFS loader for binary modules.

[Robin]

Sandboxing is an issue that has split the community before, but I'm in favour.

- To be written: A PhysFS loader for binary modules.

What, do you mean bytecode or compiled C code? Because the first should be doable already (but is not recommended), and the latter was going to be in 0.6.0 (in a slightly different form: C source code, compiled on the fly), but it was scrapped because it wasn't cross-platform enough.

[pygy]

I meant compiled C code. I arrived here right after 0.6.0 was released. What was the plan? Embeding TCC?

[Robin]

Yup. It was called love.native, but was removed again once they found out it didn't work with (IIRC) 64-bit and PPC.

[bartbes]

This discussion again? In the end nobody wants to be in jail...

[pygy]

@Jasoco: what was the problem? Linking?

@BartBes: what would it prevent in practice?

[Jasoco]

@Jasoco: what was the problem? Linking?

@BartBes: what would it prevent in practice?

What are you referring to me for? I didn't post anything in here.

But I don't care what you guys do as long as we keep the ability to just sandbox all our data in our own completely separate game-specific "data box". I don't care if we have filesystem access to outside folders or not. As long as we can still access stuff in the LOVE folder in the Library. Though if we can keep the ability to check files in other LÖVE game settings folders it would be good so we could make sequel games that will give you special things if you had beaten the first game or stuff like that.

[pygy]

:-| ... I meant Robin, sorry... The night has been very short.

[bartbes]

Yes, and why me, I mean I never said anything about preventing anything.