Joel, I got it. That's exactly what I was looking for. The impossibility of getting back what was passed to checksum makes it ideal for login routines Thanks Carlos
Em Ter 21 Out 2003 17:11, Joel Neely escreveu: > Hi, Carlos, > > You can't. See below. > > Carlos Lorenz wrote: > > Considering the following code, how can I get > > > > :pwd back in plain English? > > : > >>>write %password.txt checksum/secure pwd > >>> > >>> > >>>pwd: read %password.txt > > > > == "�'�FJ�$6�&�[/^Q�8^[&" > > Check the help for CHECKSUM: > >> ? checksum > > USAGE: > CHECKSUM data /tcp /secure /hash size /method word /key key-value > > DESCRIPTION: > Returns a CRC or other type of checksum. > CHECKSUM is a native value. > > ARGUMENTS: > data -- Data to checksum (Type: any-string) > > REFINEMENTS: > /tcp -- Returns an Internet TCP 16-bit checksum. > /secure -- Returns a cryptographically secure checksum. > /hash -- Returns a hash value > size -- Size of the hash table (Type: integer) > /method -- Method to use > word -- Method (Type: word) > /key -- Returns keyed HMAC value > key-value -- Key to use (Type: any-string) > > The description "cryptographically secure" means that it is intended > to be difficult to reverse the computation. > > -jn- > > -- > ---------------------------------------------------------------------- > Joel Neely joelDOTneelyATfedexDOTcom 901-263-4446 > > Enron Accountingg in a Nutshell: 1c=$0.01=($0.10)**2=(10c)**2=100c=$1 -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
