Kernel-Level Encryption for Game Scripts
Summary
Freelancer Client is hiring: Kernel-Level Encryption for Game Scripts.
Location: Remote
I have a set of Windows-based Python game scripts that need to be shielded from tampering and reverse engineering. My goal is to wrap the logic in an encryption layer that lives inside a custom kernel-mode driver, so the decrypted code is never exposed in user space.
What you'll do:
• Supplying concise build instructions and source (driver + loader stub) so I can reproduce the environment on future updates.
Skills: C Programming, Python, Software Architecture, C++ Programming, Debugging, Software Development, Encryption, Reverse Engineering
Budget: $30–$250 USD
Source: Freelancer Client via Remote / Online. Apply on the source website.
Original
I have a set of Windows-based Python game scripts that need to be shielded from tampering and reverse engineering. My goal is to wrap the logic in an encryption layer that lives inside a custom kernel-mode driver, so the decrypted code is never exposed in user space.
The project involves:
• Writing or adapting a Windows kernel driver that can securely store and decrypt the Python bytecode in memory only when the game process requests it.
• Updating my existing scripts so they load and execute through this protected pathway, without disrupting current functionality or performance.
• Providing a small test utility that proves the driver blocks unauthorized reads, dumps, or debuggers while the game still runs normally.
• Supplying concise build instructions and source (driver + loader stub) so I can reproduce the environment on future updates.
Successful delivery means the game launches, plays as usual, and attempts to inspect the bytecode from user space fail. If you have prior experience with Windows kernel development, driver signing, and Python embedding, we should be able to move quickly.
Location & Details
Apply on source →About this listing
This remote opportunity was imported from Freelancer and is shown here for discovery. To apply, follow the link to the original posting.