Your use of sysread is rather buggy. It can make it impossible to decode what you encoded, because sysread can return any number of bytes for any given call. This is rather moot, since we don't need to sysread from the temporary file at all.

use strict; use warnings; sub getcryptkey { return 'ABCDEFGHIJK'; } { ##### WRITER ##### my @records = ( [ 0, 1, 2 ], [ 3, 4, 5 ], [ 6, 7, 8 ], ); my $newenckey = getcryptkey(); local *PASSF; open(PASSF, ">$ENV{HOME}/.perlpasswd") or die("Can't write $ENV{HOME}/.perlpasswd: $!\n"); binmode(PASSF); my $buf = ''; foreach (@records) { # Might want to use FreezeThaw instead. $buf .= "$_->[0] $_->[1] $_->[2]\n"; print PASSF substr($buf, 0, length($newenckey), '') ^ $newenckey while (length($buf) >= length($newenckey)); } print PASSF $buf ^ substr($newenckey, 0, length($buf)); close(PASSF); } { ##### READER ##### my @records; my $newenckey = getcryptkey(); local *PASSF; open(PASSF, "<$ENV{HOME}/.perlpasswd") or die("Can't read $ENV{HOME}/.perlpasswd: $!\n"); binmode(PASSF); my $buf_e = ''; my $buf_d = ''; my $BLOCK_SIZE = length($newenckey); # Can be anything. while (sysread(PASSF, $buf_e, $BLOCK_SIZE, length($buf_e))) { $buf_d .= substr($buf_e, 0, length($newenckey), '') ^ $newenckey while (length($buf_e) >= length($newenckey)); push(@records, [ $1, $2, $3 ]) while ($buf_d =~ s/^(\S+)\s+(\S+)\s+(\S+)\n//s); } $buf_d .= $buf_e ^ substr($newenckey, 0, length($buf_e)); push(@records, [ $1, $2, $3 ]) while ($buf_d =~ s/^(\S+)\s+(\S+)\s+(\S+)\n//s); close(PASSF); require Data::Dumper; print(Data::Dumper::Dumper(\@records)); } __END__ ##### OUTPUT ##### $VAR1 = [ [ '0', '1', '2' ], [ '3', '4', '5' ], [ '6', '7', '8' ] ];

sysread and syswrite are properly used (except I don't check for errors), and the key is used from start to end.


In reply to Re: open file or pipe ? by ikegami
in thread open file or pipe ? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.