http://qs1969.pair.com?node_id=493964


in reply to File::Slurp and encryption

Try using the binmode => ':raw' option for read_file (if it's not text) and write_file (if crypt can return any byte).

Any benefit from slurping should be minimal (and null when using Big-Oh notation). You'll get real time savings by switching from the Perl version of the cypher to a C version.

Replies are listed 'Best First'.
Re^2: File::Slurp and encryption
by Solostian (Beadle) on Sep 21, 2005 at 21:01 UTC
    The encrypted file is an ASCII text originally. But an encrypted file can be handled in binary mode. I'll give it a try

    As for the Pure Perl cipher, I'm still hesitating. I know the biggest benefit would come from there but I still do not know the deployment server's OS... Any suggestion?

[reply]
      You could try to use the C cypher and fall back on the Perl one. Something like 
      my $cypher;

if (eval { require Crypt::Twofish }) {
   $cypher = 'Crypt::Twofish';
} elsif (eval { require Crypt::Twofish_PP }) {
   warn("Crypt::Twofish not found. Falling back to slower Crypt::Twofi
+sh_PP\n") if $DEBUG;
   $cypher = 'Crypt::Twofish_PP';
} else {
   die("Neither Crypt::Twofish nor Crypt::Twofish_PP was found. Aborti
+ng");
}

      [download]
      or 
      my $cypher;

foreach (qw(
   Crypt::Twofish
   Crypt::Twofish_PP
)) {
   my $mod  = $_;
   my $file = $_;

   $file =~ s{::}{/}g;
   $file .= '.pm';

   if (eval { require $file }) {
      $cypher = $mod;
      last;
   }
}

die("No acceptable encryption algorithm found. Aborting")
   if not defined $cypher;

      [download]
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom