First, could you confirm that you really need to ability to append record to an existing encrypted file?

Using my appendable format (which means you undid the Base64 encoding before storing the data): 

utf8::decode( my $s = $cipher->decrypt( read_str($fh) ) );

[download]

Using my appendable format, but left the data Base64-endoded: 

utf8::decode( my $s = $cipher->decrypt( decode_base64 ( read_str($fh) 
+) ) );

[download]

If you just dumped the return value of your encrypter to a file: 

local $/;
utf8::decode( my $s = $cipher->decrypt( decode_base64 ( <$fh> ) ) );

[download]

In reply to Re^9: line by line Encryption fun with Crypt::CBC and Rijndael? File Ownership issues? (code) by ikegami
in thread line by line Encryption fun with Crypt::CBC and Rijndael? File Ownership issues? by hmbscully

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.