Re: decrypt problem
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 56276
interpreted = N
texte = >hi all, > >running webdna 4.5, webstar 5, mac os x > >i am using this code to encrypt user passwords when saving them to the db: > >[replace >db=/data/charlotteusers.db&eqUSERIDdatarq=[id]]PASS=[encrypt >seed=[id]][url][_pass][/url][/encrypt][/replace] > >To read them back I use this: > >[decrypt seed=[userid]][unurl][pass][/unurl][/decrypt] > >id and userid are [cart] when I save the record - This works, but >there is one encrypted password in the .db that gives me nothing >when decrypted. Anyone have any thoughts? Glenn's right, you need to url the encrypted value, not encrypt the urled value: [replace db=/data/charlotteusers.db&eqUSERIDdatarq=[id]]pass=[url][encrypt seed=[id]][_pass][/encrypt][/url][/replace] .. and you don't have to unurl it when retrieving it from the db: [search db=/data/charlotteusers.db&eqUSERIDdatarq=[id]] [founditems] [decrypt seed=[id]][pass][/decrypt] [/founditems] [/search] Just don't let them change their userid value without also doing the [replace] or you'll end up with a seed that won't work with the stored pass value. -- Kenneth Grome WebDNA Programmer Outsource Service Provider Phone: +6332 255-6591 ------------------------------------------------------------- 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://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>hi all, > >running webdna 4.5, webstar 5, mac os x > >i am using this code to encrypt user passwords when saving them to the db: > >[replace >db=/data/charlotteusers.db&eqUSERIDdatarq=[id]]PASS=[encrypt >seed=[id]][url][_pass][/url][/encrypt][/replace] > >To read them back I use this: > >[decrypt seed=[userid]][unurl][pass][/unurl][/decrypt] > >id and userid are [cart] when I save the record - This works, but >there is one encrypted password in the .db that gives me nothing >when decrypted. Anyone have any thoughts? Glenn's right, you need to url the encrypted value, not encrypt the urled value: [replace db=/data/charlotteusers.db&eqUSERIDdatarq=[id]]pass=[url][encrypt seed=[id]][_pass][/encrypt][/url][/replace] .. and you don't have to unurl it when retrieving it from the db: [search db=/data/charlotteusers.db&eqUSERIDdatarq=[id]] [founditems] [decrypt seed=[id]][pass][/decrypt] [/founditems] [/search] Just don't let them change their userid value without also doing the [replace] or you'll end up with a seed that won't work with the stored pass value. -- Kenneth Grome WebDNA Programmer Outsource Service Provider Phone: +6332 255-6591 ------------------------------------------------------------- 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://webdna.smithmicro.com/
Kenneth Grome
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:
quitting (1997)
Bug Report, maybe (1997)
cybercash on OSX - was Executing remote AppleScript (2000)
InternetWeek E-Commerce article (1998)
Web Merchant process after credit card clears (1998)
WebTen and WebCat (1997)
foreign languages, email, webcat (1998)
Separate SSL Server (1997)
[lookup] is case-sensitive, [lookup] is case sensitive... (2003)
ShowIf & HideIf Question? (1998)
A Current Feature or Futre Concept (1998)
webcatalog [date] bug (1999)
PCS Frames (1997)
WebCat for mass emailings (1997)
TCP Connect (2000)
Dark Horse Comics success story (1997)
Bug Report, maybe (1997)
DNS Lookup 2 (2000)
shipcost (1997)
Thanks Grant (1997)