Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Suggestion] - Section for the best ways to secure your Godot application? #1

Open
girng opened this issue Jan 12, 2019 · 3 comments
Open
Labels
enhancement New feature or request

Comments

@girng
Copy link

girng commented Jan 12, 2019

I know there is a small portion in the official godot docs, but I think it would be relevant/beneficial in this repo as well. Maybe a section for tricks to "maximize the security" of your Godot app? For example, changing the XOR key before compiling adds one extra step the hacker has to do, etc.

Awesome repo btw, I'm learning a lot.

@bruvzg bruvzg added the enhancement New feature or request label Jan 21, 2019
@waleed177
Copy link

waleed177 commented Mar 24, 2022

I dont consider encrypting the game as security, in my opinion, security is only when protecting the user against others (including the developer). If its multiplayer, security should be server side (protecting the server from the client) and client-side (protecting the client from the server, i.e, no arbitrary code execution, etc..).

@nikitalita
Copy link
Collaborator

Your best option is probably to just encrypt the PAK, but the key is trivially recoverable from the EXE. We don't include instructions on how to do that, though, so it would protect from at least the most basic of RE attempts.

@manjaroman2
Copy link

The engine in open source, that's the problem
Game devs who want to secure their game need to modify the engine code.
The load_byte_code function is a good start, you can go lower modify the mbedtls library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants