Skip Menu |

This queue is for tickets about the Filter-Crypto CPAN distribution.

Report information
The Basics
Id: 38776
Status: resolved
Priority: 0/
Queue: Filter-Crypto

People
Owner: Nobody in particular
Requestors: erikweidel [...] web.de
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in:
  • 1.21
  • 1.22
Fixed in: (no value)



Subject: unencrypted copy in directory "lib"
When creating a simple exe file with this command "pp -M Filter::Crypto::Decrypt -f Crypto -o testhello.exe testhello.pl" and starting the exe, there is an unencrypted testhello.pl in the directory C:\Dokumente und Einstellungen\eweidel\...\par-eweidel\cache-d1492d4a8e08a9e745068a62fa998b347eb19f4\inc\lib ! The file in ...\inc\script is encrypted correctly. BTW: Thanks very much for the quick reaction concerning bug #38638. Makes life much easier not having to list every single module that is to be encrypted :-))
On Thu Aug 28 03:41:45 2008, erikweidel wrote: Show quoted text
> When creating a simple exe file with this command > "pp -M Filter::Crypto::Decrypt -f Crypto -o testhello.exe > testhello.pl" > and starting the exe, there is an unencrypted testhello.pl in the > directory > C:\Dokumente und > Einstellungen\eweidel\...\par-eweidel\cache- > d1492d4a8e08a9e745068a62fa998b347eb19f4\inc\lib > ! > The file in ...\inc\script is encrypted correctly.
I'm unable to reproduce this problem. I created a simple "testhello.pl" script containing just: print "Hello, world.\n"; and pp-ed it using the same command as you: pp -M Filter::Crypto::Decrypt -f Crypto -o testhello.exe testhello.pl When I run it, it creates a cache folder under "C:\Documents and Settings\shay\Local Settings\Temp\par-shay". That contains an encrypted inc/script/testhello.pl, but no testhello.pl at all in inc/lib. This is as I would expect. I'm surprised that you're getting a testhello.pl in inc/lib at all, never mind whether it is encrypted or not! The contents of the cache folder should mimic the contents of the testhello.exe, which is actually a ZIP file, and can be opened with programs like WinZip. If open my testhello.exe in WinZip then I find that it does indeed contain an encrypted inc/script/testhello.pl and no inc/lib/testhello.pl. What does your testhello.exe contain? Try (manually) clearing out your "C:\Dokumente und Einstellungen\eweidel\...\par-eweidel" directory, then running testhello.exe again, to ensure that it is creating a fresh cache folder. Does it still contain inc/lib/testhello.pl this time? If this is still a problem for you then it is probably down to the PAR framework itself, rather than my PAR::Filter subclass. My subclass simply gets called by the framework for a series of files, so if it isn't encrypting something that it should be then it probably means that the PAR framework hasn't asked my filter to encrypt it. Try repeating the exercise with another PAR::Filter subclass, e.g. the Bleach filter that comes with PAR. If you still get two copies of testhello.pl, one "bleached" and the other not, then it is definitely a problem with the framework rather than with individual filters. What versions of things are you using? I've tried with two different set-ups, and can't reproduce your problem either way: perl-5.8.6 PAR-0.85 PAR-Dist-0.07 PAR-Packer-0.12 perl-5.8.8 PAR-0.976 PAR-Dist-0.31 PAR-Packer-0.976 HTH, Steve
From: erikweidel [...] web.de
On Fr. 29. Aug. 2008, 03:42:13, SHAY wrote: Show quoted text
> On Thu Aug 28 03:41:45 2008, erikweidel wrote:
> > When creating a simple exe file with this command > > "pp -M Filter::Crypto::Decrypt -f Crypto -o testhello.exe > > testhello.pl" > > and starting the exe, there is an unencrypted testhello.pl in the > > directory > > C:\Dokumente und > > Einstellungen\eweidel\...\par-eweidel\cache- > > d1492d4a8e08a9e745068a62fa998b347eb19f4\inc\lib > > ! > > The file in ...\inc\script is encrypted correctly.
> > I'm unable to reproduce this problem. > > I created a simple "testhello.pl" script containing just: > > print "Hello, world.\n"; > > and pp-ed it using the same command as you: > > pp -M Filter::Crypto::Decrypt -f Crypto -o testhello.exe testhello.pl > > When I run it, it creates a cache folder under "C:\Documents and > Settings\shay\Local Settings\Temp\par-shay". That contains an encrypted > inc/script/testhello.pl, but no testhello.pl at all in inc/lib. > > This is as I would expect. I'm surprised that you're getting a > testhello.pl in inc/lib at all, never mind whether it is encrypted or not! > > The contents of the cache folder should mimic the contents of the > testhello.exe, which is actually a ZIP file, and can be opened with > programs like WinZip. If open my testhello.exe in WinZip then I find > that it does indeed contain an encrypted inc/script/testhello.pl and no > inc/lib/testhello.pl. What does your testhello.exe contain? > > Try (manually) clearing out your "C:\Dokumente und > Einstellungen\eweidel\...\par-eweidel" directory, then running > testhello.exe again, to ensure that it is creating a fresh cache folder. > Does it still contain inc/lib/testhello.pl this time? > > If this is still a problem for you then it is probably down to the PAR > framework itself, rather than my PAR::Filter subclass. My subclass > simply gets called by the framework for a series of files, so if it > isn't encrypting something that it should be then it probably means that > the PAR framework hasn't asked my filter to encrypt it. > > Try repeating the exercise with another PAR::Filter subclass, e.g. the > Bleach filter that comes with PAR. If you still get two copies of > testhello.pl, one "bleached" and the other not, then it is definitely a > problem with the framework rather than with individual filters. > > What versions of things are you using? > > I've tried with two different set-ups, and can't reproduce your problem > either way: > > perl-5.8.6 > PAR-0.85 > PAR-Dist-0.07 > PAR-Packer-0.12 > > perl-5.8.8 > PAR-0.976 > PAR-Dist-0.31 > PAR-Packer-0.976 > > HTH, > Steve
I did a fresh install of Active Perl and PAR::Packer on a different computer. Here the problem does not occur so you can close the bug ! I will try to investigate this a bit further to find out where the difference between the installations is and what causes this effect. Mysterious, mysterious !! Thanks for your help ! Erik
Okay, I'm closing this bug. Let me know if it does turn out to be a problem with this module, but from the sound of things, I don't think it will.