RE: RE: Re: peeking at the working interpreter

The -d option is disabled when you use the decrypt template from the Filter module at CPAN

Good move.

Try hitting it with perl -MO=Deparse file.pl and see what you get. Deparse uses the internal compiled structure, maybe you'll get lucky? with that. I don't know if you'll be able to run the B:: modules without the debugger (I've never compiled perl without it) so I'm just guessing here :)

/brother t0mas

Comment on RE: RE: Re: peeking at the working interpreter

Replies are listed 'Best First'.
RE: (Deparse) peeking at the working interpreter by gregorovius (Friar) on Sep 06, 2000 at 20:07 UTC
Here's what I get with Deparse: `[C:/TEMP] perl -MO=Deparse not_encrypted.pl print "hello world\n"; ... [C:/TEMP] perl -MO=Deparse encrypted.pl Aborting, Compiler detected at d:/Claudio/Perl/lib/DynaLoader.pm line +219. Compilation failed in require at encriptado.pl line 1. BEGIN failed--compilation aborted at encriptado.pl line 1.` [download] This is the code in the decrypt.xs template that cares for this: `/* Check for the presence of the Perl Compiler */ if (gv_stashpvn("B", 1, FALSE)) croak("Aborting, Compiler detected") ;` [download] Thanks for the help!	[reply] [d/l] [select]
RE: RE: (Deparse) peeking at the working interpreter by t0mas (Priest) on Sep 06, 2000 at 20:18 UTC
It seems they've been thinking a bit :) If I where your customer, I would now have to disassemble your perl.exe and try to reverse engineer your decrypt algorithm the usual way, or pay the $60K USD... /brother t0mas	[reply]
RE: RE: RE: (Deparse) peeking at the working interpreter by tye (Sage) on Sep 06, 2000 at 20:30 UTC
Nah, just use a debugger on Perl, request the Perl debugger, and use the first debugger to disable the detection of the second debugger. Just hard enough to give you several opportunities to reconsider why you are trying to see what the author really didn't want you to see. Certainly makes it easy to prove intent if you have to sue. (: - tye (but my friends call me "Tye")	[reply]