in reply to Re^6: line by line Encryption fun with Crypt::CBC and Rijndael? File Ownership issues? (code)
in thread line by line Encryption fun with Crypt::CBC and Rijndael? File Ownership issues?
If I have to encrypt something on an outside machine and decrypt it at my end (using the encrypter and decrypter above), do they both have to be the same endian?
If you store 0x11223344 into the file, you'd rather not read 0x44332211 from the file.
Thank you very much for your help. I changed the pack/unpack to little-endian order and that worked
I used 'N', which produces the same encoding on all systems. Why did you change it?
Could I use your recommendation above to encrypt and decrypt large files (about 3 million records) or would you have any suggestions or reference points you could guide me to?
The format is efficient for appending records semi-frequently, but it's quite wasteful otherwise. Your 300MB might very well take up 600MB, and it could take a while to decode.
If you have a write-once-read-often scenario, you'd be better off converting the record file into a normal (single encryption session) file before doing your reading.
An alternative to the entire approach would be to have a persistent deamon which handles writting to the file (as a single encryption session). This would definitely be better if you had a near-constant stream of records to write.
my entire charset on the terminal gets funky.
Programs control the terminal by sending special character sequences in-band. The encrypted data can contain any characters, including some that resemble terminal control sequences.
more and/or less replace "dangerous" characters with representative glyphs. There's also od.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^8: line by line Encryption fun with Crypt::CBC and Rijndael? File Ownership issues? (code)
by samip (Novice) on Jul 31, 2008 at 14:57 UTC | |
by ikegami (Patriarch) on Jul 31, 2008 at 20:30 UTC | |
by samip (Novice) on Aug 01, 2008 at 15:11 UTC | |
by ikegami (Patriarch) on Aug 01, 2008 at 20:48 UTC | |
by samip (Novice) on Aug 01, 2008 at 23:18 UTC | |
| |
by samip (Novice) on Aug 04, 2008 at 17:51 UTC |