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

Encrypt and embed static resources (js/css/images) inside phpdesktop executable #18

Open
GoogleCodeExporter opened this issue Aug 28, 2015 · 8 comments

Comments

@GoogleCodeExporter
Copy link

We need a way to protect the www/ directory, using php encoder
is an option, but it won't protect other files in the www
directory.

Before we start work on thiss issue we need to implement Chrome 
engine (Issue 1) and PHP API calls (Issue 3).

If the www directory is embedded in zip file, we should not extract
it anywhere to the file system, the best way is to extract it to
memory, so that it's really hidden. But doing it this way won't
work with web-server (unless we modify web-server to work with our
virtual in-memory filesystem). In Chrome web-server is not needed,
as there Scheme handler that acts similarly to a web-server.

For keeping www directory in memory we will probably need some kind
of Virtual File System.

To execute PHP scripts that aren't accessible through local file
system we would have to hook up to the PHP API (Issue 3).

The www directory can be encrypted in a zip file using AES encryption,
we could use this simple C++ library:
http://www.lomont.org/Software/Misc/AES/AES.php

We will also need some zip library.

An option for the zip file to reside along with the exe file (
data.zip or data.dat - the zip filename could be customized through
settings.json file).

The best option would be to embed that zip file in exe file as
a resource.

Some tool for automating the process of encrypting zip file and
embedding it in exe file would be useful.

Original issue reported on code.google.com by [email protected] on 2 Feb 2013 at 3:13

Repository owner deleted a comment from GoogleCodeExporter Jun 11, 2017
Repository owner deleted a comment from GoogleCodeExporter Jun 11, 2017
Repository owner deleted a comment from GoogleCodeExporter Jun 11, 2017
Repository owner deleted a comment from GoogleCodeExporter Jun 11, 2017
Repository owner deleted a comment from GoogleCodeExporter Jun 11, 2017
Repository owner deleted a comment from GoogleCodeExporter Jun 11, 2017
Repository owner deleted a comment from GoogleCodeExporter Jun 11, 2017
Repository owner deleted a comment from GoogleCodeExporter Jun 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@cztomczak @GoogleCodeExporter and others