Re: Crypt::CipherSaber replacement... Crypt::CBC?

As Marshall++ said, RC4 isn't completely busted yet so it's probably fine to stick with it. If you're looking to change your cipher you might want to move to Crypt::CBC and the Advanced Encryption Standard aka Crypt::Rijndael.

As far as plain text goes, MIME::Base64 might be what you're reaching for.

Comment on Re: Crypt::CipherSaber replacement... Crypt::CBC?

Replies are listed 'Best First'.
Re^2: Crypt::CipherSaber replacement... Crypt::CBC? by Marshall (Canon) on Apr 30, 2010 at 11:14 UTC
I think base64 is a great way to go! Mime-Base64-3.09 looks good and is available on ActiveState also. The wikipedia has a good explanation of base64. Convert-UU-0.5201 is an older technology. See wiki at uuencoding. The main point is to get this 8 bit binary stuff into printable ASCII stuff that won't get "mangled" I found this wiki article interesting: Cipher-block_chaining.	[reply]
Re^3: Crypt::CipherSaber replacement... Crypt::CBC? by rowdog (Curate) on Apr 30, 2010 at 21:31 UTC
uuencoding looks good but Crypt::CBC provides encrypt_hex() and decrypt_hex() so I guess I'd go with hex if I was moving to Crypt::CBC anyhow.	[reply]
Re^2: Crypt::CipherSaber replacement... Crypt::CBC? by rowdog (Curate) on Apr 30, 2010 at 21:14 UTC
The other parameter is Pure-Perl implementation of whatever solution seems to be the most plausible. Oops, I missed that requirement the first time. Pure Perl implementations of ciphers will be much slower and will limit your choices. That said, Crypt::CBC + Crypt::Rijndael_PP or Crypt::Twofish_PP might work for you. I agree with hardburn that RC4 is tricky to implement correctly and should generally be avoided unless you really know what you're doing and you have a real reason to use that particular cipher.	[reply]