| 1 |
|
| 2 |
Embperl - Building dynamic Websites with Perl |
| 3 |
--------------------------------------------- |
| 4 |
|
| 5 |
Copyright (c) 1997-2008 Gerald Richter / ecos gmbh www.ecos.de |
| 6 |
Copyright (c) 2008-2014 Gerald Richter |
| 7 |
|
| 8 |
You may distribute under the terms of either the GNU General Public |
| 9 |
License or the Artistic License, as specified in the Perl README file. |
| 10 |
|
| 11 |
THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED |
| 12 |
WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF |
| 13 |
MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. |
| 14 |
|
| 15 |
$Id: README 1578075 2014-03-16 14:01:14Z richter $ |
| 16 |
|
| 17 |
|
| 18 |
Sourcecode encryption |
| 19 |
===================== |
| 20 |
|
| 21 |
Embperl has the possibility to use encrypted sourcefiles. This allows |
| 22 |
to hide your code from curious people or make sure nobody can modify |
| 23 |
your code. |
| 24 |
|
| 25 |
To enable encrypted sourcefile, go to the crypto directory and edit |
| 26 |
the epcrypto_config.h file. Here you can enable/disable encryption, |
| 27 |
choose which algorithmus to use, the encryption key and whenever |
| 28 |
Embperl should still work with unencrypted files. Make sure to use a |
| 29 |
unique encryption key. Additionally OpenSSL must be already installed |
| 30 |
on your system. Now install Embperl as usual, by running |
| 31 |
|
| 32 |
perl Makefile.PL |
| 33 |
make |
| 34 |
make test |
| 35 |
make install |
| 36 |
|
| 37 |
To encrypt your source files go to the crypto directory and start the |
| 38 |
epcrypto program. It takes a source and a destination filename. If you |
| 39 |
are using Embperl 2.x, you have to specify the syntax the sourcefile |
| 40 |
uses as third parameter, if it is any other than "Embperl". |
| 41 |
|
| 42 |
IMPORTANT: Make sure to not distribute any files from the crypto |
| 43 |
directory, because it contains the key. Anybody who |
| 44 |
has access to the crypto directory, can decrypt your |
| 45 |
sourcefiles. |
| 46 |
|
| 47 |
The encrytion key is compiled into the binary, because |
| 48 |
Embperl needs it to do the decryption, so anybody who |
| 49 |
has access to the binary _and_ is able to disassemble |
| 50 |
the binary code, will be able to retrieve the key. |
| 51 |
So sourcecode encrytion can hide your source code |
| 52 |
from most people, because it's hard to disasemble the binary |
| 53 |
and get the key, but if anybody really wants your code |
| 54 |
he will get it! To prevent this the key shouldn't be |
| 55 |
compiled into the binary, but instead a C function |
| 56 |
should be given, that could retrieve the key from a |
| 57 |
save place, e.g. a smart card, even better would |
| 58 |
be to do the decrytion directly on the smart card. |
| 59 |
|
| 60 |
|
| 61 |
|
| 62 |
|
| 63 |
|