Softcode encryption functions issue...

Quoting noltar@korongil.org (noltar@korongil.org):
> 1.7.7p11
> 
> This is an issue with the encrypt and decryp I noticed just recently, and am 
> not sure if anyone else has ever noticed it...
> 
> Essentially, if you use the encrypt and decrypt softcode functions with a 
> password that includes numbers, the output of the encrypt function is so 
> loaded with special characters, such as % ( ) \ , { } [ ],  that it is 
> essentially impossible to decrypt the text due to the parsing of those 
> characters. I know these sometimes appear when using all text passwords, 
> notably [ ] and \, but they are not nearly as common. In any case, I wanted to 
> bring it up if for some reason it hasn't been in the past, and wonder if 
> perhaps there was some way of correcting the behavior to make it less 
> difficult to deal with.

It's true that encrypt returns these characters, but not true that you
can't decrypt them. I have shown people how to do so (by ensuring
that you protect the output appropriately from extra evaluation).

However, I'd be happy to add a second encrypt/decrypt pair that
spews in base64 - probably once I get to SSL support in general,
as the SSL library provides this.

 - Alan

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Javelin@M*U*S*H (mush.pennmush.org 4201) |           Alan Schwartz
                                         |       dunemush@pennmush.org
Paul@DuneMUSH, and Javelin elsewhere     |     PennMUSH Server Maintainer
=-------------------------------------------------------------------------=
   PennMUSH God's Guide: http://www.pennmush.org/~alansz/guide.html
        PennMUSH Source: http://ftp.pennmush.org/Source
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

base64 encryption armoring

encrypt64() and decode64()?