diff options
| author | Jarkko Hietaniemi <jhi@iki.fi> | 2001-05-05 18:16:00 +0000 |
|---|---|---|
| committer | Jarkko Hietaniemi <jhi@iki.fi> | 2001-05-05 18:16:00 +0000 |
| commit | 83df6a1d65c0fba9c27c7fb715fa674b03462cf0 (patch) | |
| tree | 0a054e0b4530814c38513f458ed5af5083134f14 /pod/perlsec.pod | |
| parent | 8fc2f983bc0c066c9be215d0b6cf72814390f573 (diff) | |
| download | perl-83df6a1d65c0fba9c27c7fb715fa674b03462cf0.tar.gz | |
Updates on the pods related to the modules included since 5.6.
TODO: perltodo really could use major updating.
p4raw-id: //depot/perl@9998
Diffstat (limited to 'pod/perlsec.pod')
| -rw-r--r-- | pod/perlsec.pod | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/pod/perlsec.pod b/pod/perlsec.pod index 3870c2ef70..18c25eee44 100644 --- a/pod/perlsec.pod +++ b/pod/perlsec.pod @@ -343,10 +343,11 @@ determine the insecure things and exploit them without viewing the source. Security through obscurity, the name for hiding your bugs instead of fixing them, is little security indeed. -You can try using encryption via source filters (Filter::* from CPAN). -But crackers might be able to decrypt it. You can try using the -byte code compiler and interpreter described below, but crackers might -be able to de-compile it. You can try using the native-code compiler +You can try using encryption via source filters (Filter::* from CPAN, +or Filter::Util::Call and Filter::Simple since Perl 5.8). +But crackers might be able to decrypt it. You can try using the byte +code compiler and interpreter described below, but crackers might be +able to de-compile it. You can try using the native-code compiler described below, but crackers might be able to disassemble it. These pose varying degrees of difficulty to people wanting to get at your code, but none can definitively conceal it (this is true of every |