> You are correct. If you...
>
> use Hidden::Module
>
> then use Data::Dumper to reconstruct most of the raw code. This would be
> about as useful as decompiling 'B' code. If you had access to the
> intrepreter directly, you could probably even capture the decrypt stream
> before perl compiles i
>> BZS::License performs a similar load operation to BZS::Loader. First,
>> however it looks for a hash pointer in the caller program called
>> $ptr2_License.
>> The hash contains the path to the License file and an optional
>>'private' key
>> list of modules which will decrypt only with the 'priv
Michael Robinton wrote:
> see attached
[...]
> BZS::License performs a similar load operation to BZS::Loader. First,
> however it looks for a hash pointer in the caller program called $ptr2_License.
> The hash contains the path to the License file and an optional 'private' key
> list of modules
see attached
=head1 NAME
BZS::License - Perl extension to examine a license file.
=head1 USEAGE
There are two modes of operation:
use BZS::License;1;
__END__
encrypted module here...
The calling routine should define an anonymous hash pointed to by the
On Mon 22-Jul-2002 at 10:15:44AM -0400, Jon wrote:
> At my former employer's, we built an Enterprise Management System out of
> mod_perl. He wants to distribute it to clients w/o risking theft of his
> code.
We had the same thoughts here, but we arrived at the conclusion that
there is one very ef
Jon,
I've been doing some thinking along these lines (for website security,
not for releasing code). I don't have a solution, but below are some
thoughts I've had. I would love to hear from anyone who knows solutions
for any of the points below. Most of the thoughts below are based on
encrypti
> On Mon, 22 Jul 2002 10:17:21 -0500 (CDT), Dave Rolsky <[EMAIL PROTECTED]> said:
>> use Filter::decrypt ;
>> ÿ £j¨tBÃavð@¥£hK6'{'ÂÃ^zÂ'
>> []
>>
>>
>> Of course, perl itself (or mod_perl) sees the cleartext, so a good
>> hacker will find a way to break it.
>
On Mon, 22 Jul 2002, Andreas J. Koenig wrote:
> > On Mon, 22 Jul 2002 13:10:25 +1000, Iain Truskett <[EMAIL PROTECTED]> said:
>
> > As far as I know, there's no good way to do it. It is Perl after all.
> > And with mod_perl things just get trickier.
>
> Filter::decrypt does that. It's ver
Hi
( 02.07.22 10:15 -0400 ) Jon:
> At my former employer's, we built an Enterprise Management System out of
> mod_perl. He wants to distribute it to clients w/o risking theft of his
> code.
Well, I'll save the intellectual property rant, but it's going to be
very difficult to do. Perl is set up
Hi!
On Sun, Jul 21, 2002 at 10:58:24PM -0400, Jonathon M. Robison wrote:
> Anyone know offhand a good way to hide your perl code when using
> mod_perl? Acme::Bleach isn't doing it - httpd is failing to start on
You could write an obfuscator. Maybe Acme::EyeDrop works?
See
http://domm.zsi.at/
> At my former employer's, we built an Enterprise Management System out of
> mod_perl. He wants to distribute it to clients w/o risking theft of his
> code.
If "w/o risking theft" means "eliminating risk of theft", then he can't
do it. He can lower risk to some degree, but it can't be eliminated
At my former employer's, we built an Enterprise Management System out of
mod_perl. He wants to distribute it to clients w/o risking theft of his
code.
--Jon R.
PGP Key fingerprint = 12 DA FC 06 AB 4C D6 A4 DE 03 E0 77 D6 DE E0 73
PGP public key available by fingering [EMAIL PROTECTED]
On Mon,
-- [EMAIL PROTECTED] on 07/22/02 09:15:23 -0400
> Thanks, Iain! This helps explain some problems I ran into when I tried to use
> Switch. ;-) Wish the Switch docs included some caveats about using it with
> mod_perl
Switch, Multifiles, Q::S, and A::B all have a Caveat Utilitor
note in the
Wesley Sheldahl/Lex/Lexmark)
Subject: Re: Hiding perl code
* Jonathon M. Robison ([EMAIL PROTECTED]) [22 Jul 2002 13:03]:
> Anyone know offhand a good way to hide your perl code when using
> mod_perl? Acme::Bleach isn't doing it - httpd is failing to start on
> initial test [...]
Acme
> On Mon, 22 Jul 2002 13:10:25 +1000, Iain Truskett <[EMAIL PROTECTED]> said:
> As far as I know, there's no good way to do it. It is Perl after all.
> And with mod_perl things just get trickier.
Filter::decrypt does that. It's very hard to break as you compile a
self-made key statically
* Jonathon M. Robison ([EMAIL PROTECTED]) [22 Jul 2002 13:03]:
> Anyone know offhand a good way to hide your perl code when using
> mod_perl? Acme::Bleach isn't doing it - httpd is failing to start on
> initial test [...]
Acme::Bleach is a source filter. Source filters will just screw up your
mod
Anyone know offhand a good way to hide your perl code when using
mod_perl? Acme::Bleach isn't doing it - httpd is failing to start on
initial test, and then on second test I find that httpd.conf suddenly
got a 'use Acme::Bleach' inserted at line 1 and the whole thing is bleached.
Perhaps perl2
17 matches
Mail list logo