bliako has asked for the wisdom of the Perl Monks concerning the following question:
Wise Monks, please advice on how to use Filter::Crypto::CryptFile via PAR so as to primarily encrypt my source files but also control access to them (on a hosted, entirely mine, bare-metal linux)
Ideally, I want to be asked for a password/key at encryption stage and then asked just once (and not once for each module included!) each time the pp-executable is run. Is this too far-fetched? May be there is yet another module to allow for encrypting and also controlling access to the script?
The manpage states that the following will encrypt my script and all modules used by the script:
pp -f Crypto -M Filter::Crypto::Decrypt -o hello hello.plFine! But I was expecting to be asked for a password/key. Instead, I was asked for password once during installation of Filter::Crypto::CryptFile and then no password required when running the pp-exe script.
bw, bliako
p.s. As to why I want to do that: I feel I have contributed enough public-domain software so as not to be asked this question.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Encrypting source code :(
by soonix (Canon) on Dec 27, 2018 at 15:58 UTC | |
by bliako (Monsignor) on Dec 27, 2018 at 17:13 UTC | |
Re: Encrypting source code :(
by RonW (Parson) on Jan 04, 2019 at 22:42 UTC | |
by bliako (Monsignor) on Jan 05, 2019 at 14:58 UTC | |
by kschwab (Vicar) on Jan 05, 2019 at 18:11 UTC | |
by bliako (Monsignor) on Jan 06, 2019 at 11:02 UTC | |
by RonW (Parson) on Jan 09, 2019 at 21:24 UTC | |
by RonW (Parson) on Jan 09, 2019 at 21:09 UTC | |
by bliako (Monsignor) on Jan 10, 2019 at 12:21 UTC | |
by Anonymous Monk on Jan 05, 2019 at 12:16 UTC |