steve-m-hay / filter-crypto Goto Github PK

Hi,

Sorry to interrupt， how can we exec the ./a.pl instead of perl ./a.pl after encryption ?

When a simple hello word script a.pl
#!/usr/bin/perl print ("Hello World\n");
be encrypted by the script/crypt_file -i a.pl，then the a.pl turns into an ASIIC file, and with the first line:
use Filter::Crypto::Decrypt;

If calling the ./a.pl from the shell，will produce error
./a.pl: line 1: use: command not found
Where the script is interpreted as the shell script;

How can we just call ./a.pl ( instead of perl ./a.pl ) and make the script interpreted by perl ?

Thank you ~

Hello,
I want to konw why I use command 'cpanm Filter::Crypto' or 'perl -MCPAN -e shell 'install Filter::Crypto'' to install this moudle in Ubuntu system, it will be error to query me 'Where is your OpenSSL? [/usr]' although my openssl path was set usr. however, it still have this error so that cannot to install, so could you give me some suggestion about this.

Shuai

Hi,
I'm not able to install Filter-Cryto in Rockylinux 9
which uses openssl 3.0.1.

Thanks
JDM

I am trying to install Filter::Crypto on Windows 10, Cygwin:

$ perl --version
This is perl 5, version 30, subversion 3 (v5.30.3) built for x86_64-cygwin-threads-multi
(with 7 registered patches, see perl -V for more detail)
$ wget https://cpan.metacpan.org/authors/id/S/SH/SHAY/Filter-Crypto-2.09.tar.gz
$ tar zxvf Filter-Crypto-2.09.tar.gz
$ cd Filter-Crypto-2.09
$ perl Makefile.PL
Where is your OpenSSL? [/usr]
Found include directory ............ /usr/include
Found OpenSSL version .............. 1.1.1f
Error (109): No OpenSSL crypto library found at Makefile.PL line 67.

The library is located in /usr/lib:

$ ls /usr/lib/libcrypto.dll.a
/usr/lib/libcrypto.dll.a

Hi,
Nothing is preventing me to load Filter::Crypto::Decrypt and, then, B::Deparse before run encrypted script:

Decrypt.pm

package Decrypt;
require Filter::Crypto::Decrypt;
require B::Deparse;
1;
__END__

$ perl -M"Decrypt" ./encypted.pl

So, this protection is useless and easily can be avoided.

But it prevents to load encrypted modules after B was loaded by some package.
For example, Sub::Quote using B.
This just adding headache, but not extra protection.

I think, that check for B::Deparse presence can be removed.