You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 2 Feb 2013 at 3:13The text was updated successfully, but these errors were encountered: