more useful options | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
I'm doing just that for my network "backup buddy" program!
I settled on a in-script implementation of CyberSaber to avoid tons of modules and dependancies. In my script, the password is right there in the config, because if you could read that script, you could read the files too. No, you should not need to break up the file yourself. Any module worth its salt should have an initialization phase followed by multiple calls to a feeder function where you shovel in a bufferfull and get the encoded text out. Keep calling that, followed by a final flush call. Re key and password length: Except for RC4/CyberSaber, the key is a binary value generated from a password by some algorithm such as a cryptographic hash. The length of the password has nothing to do with the final key size. If you want the big guns, rather than a simple in-script implementation, go right to Crypt::OpenPGP. It's new, it's awsome, and it's standard RFC2440 compliant. —John In reply to Re: Encrypting Largish Files
by John M. Dlugosz
|
|