Re: [search] & [encrypt]/[decrypt]
This WebDNA talk-list message is from 2001
It keeps the original formatting.
numero = 38497
interpreted = N
texte = Not to fuel a feud, but in this case Ken is right and Grant is wrong...If you specify the seed parameter (even if specified as blank) in an encrypt context, your resulting encrypted string will be different from one encryption to the next, so you CANNOT compare (or search) the encrypted strings, but you CAN decrypt the string and compare, view or use as you wish. Useful for sensitive data (such as credit card numbers).If you do NOT specify the seed parameter in an encrypt context, your resulting encrypted string will be the same every time, so you CAN compare (or search for a full string match, not partial strings) the encrypted values, but you CANNOT decrypt the string. Useful for passwords and little else.- BrianAt 11:38 PM 9/6/2001, Grant Hulbert wrote:> >Webcat reportedly creates a different encryption string, or at >least not the exact same string, every time it performs an >encryption on the same original string.>>Uh, no, then this would make the built-in one-way encrypted password >system not work. What you are talking about does happen when no >seed value is provided, but in the examples provided by James, a >seed value is clearly in use.-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list
.To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Not to fuel a feud, but in this case Ken is right and Grant is wrong...If you specify the seed parameter (even if specified as blank) in an encrypt context, your resulting encrypted string will be different from one encryption to the next, so you CANNOT compare (or search) the encrypted strings, but you CAN decrypt the string and compare, view or use as you wish. Useful for sensitive data (such as credit card numbers).If you do NOT specify the seed parameter in an encrypt context, your resulting encrypted string will be the same every time, so you CAN compare (or search for a full string match, not partial strings) the encrypted values, but you CANNOT decrypt the string. Useful for passwords and little else.- BrianAt 11:38 PM 9/6/2001, Grant Hulbert wrote:> >Webcat reportedly creates a different encryption string, or at >least not the exact same string, every time it performs an >encryption on the same original string.>>Uh, no, then this would make the built-in one-way encrypted password >system not work. What you are talking about does happen when no >seed value is provided, but in the examples provided by James, a >seed value is clearly in use.-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Brian Fries
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
WC Database Format (1997)
in string ??? (2001)
webcat- multiple selection in input field (1997)
Template not found error messages (1997)
Mac: [ListFiles] bug alert (1997)
Linux Beta4 Problem (2000)
Questions (1998)
WebCat2b13MacPlugIn - [shownext method=post] ??? (1997)
Blowback and budgets. (2000)
Simple counter - how? (1997)
Webmerch Error (1998)
FoundItems Question (1998)
Capturing the referring site (1999)
WebCat2 - storing unformatted date data? (1997)
fieldType=num (1997)
Suffix or Line? (1999)
WebCommerce: Folder organization ? (1997)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
For those of you not on the WebCatalog Beta... (1997)
Emailer choke (1997)