Re: [encrypt] blues....

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 31456
interpreted = N
texte = >At 4:45 PM 5/4/00, JHowarth@smithmicro.com wrote: >>I apologize for my incomplete answer before. >> >>Use [encrypt] without a seed value. The text will be encrypted the same way >>every time, so the compare will work. >> >>Thanks Ken for pointing out that seeded encrypted values are not always the >>same. Which is why some times his encrypt/decrypts do not work. > >No no no... Granted (no pun intended) that the encrypted values are >different each time through the results page, but when decrypted they >should yield the same result. > >[encrypt seed=joe]123[/encrypt] might yield bbbbb >and >[encrypt seed=joe]123[/encrypt] might yield xxxxx >and >[encrypt seed=joe]123[/encrypt] might yield yyyyy > >then > >[decrypt seed=joe]yyyyy[/decrypt] should yield 123 >[decrypt seed=joe]xxxxx[/decrypt] should yield 123 >[decrypt seed=joe]bbbbb[/decrypt] should yield 123 > >You see we don't really store the encrypted value, we're just >encrypting it to pass it in a URL. We use the decrypted value as the >key into the database to retreive the record. > >so my link looks like: > > > > >then on the display.tpl page I have: > >[search..... &eqMEMBERIDdatarq=[unurl][decrypt >seed=joe][who][/decrypt][/unurl]] > >Help? Well let's see ... yes, it looks like you've urled the value after you've encrypted it, which makes sense -- but that only means you have to remember to unurl it BEFORE you try to decrypt it, not afterwards.And since you're using the decrypted value in a search context, you had better be sure to url the decrypted value, to be sure it doesn't have any & characters in it which would screw p your search string.Why don't you try this, I think it will work just fine:[search..... &eqMEMBERIDdatarq=[url][decrypt seed=joe][unurl][who][/unurl][/decrypt][/url]] ================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- 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 Associated Messages, from the most recent to the oldest:

    
  1. Re: [encrypt] blues.... (Joseph D'Andrea 2000)
  2. Re: [encrypt] blues.... (Kenneth Grome 2000)
  3. Re: [encrypt] blues.... (Joseph D'Andrea 2000)
  4. Re: [encrypt] blues.... (Kenneth Grome 2000)
  5. Re: [encrypt] blues.... (JHowarth@smithmicro.com 2000)
  6. Re: [encrypt] blues.... (Kenneth Grome 2000)
  7. Re: [encrypt] blues.... (JHowarth@smithmicro.com 2000)
  8. [encrypt] blues.... (Joseph D'Andrea 2000)
  9. Saturday [encrypt] blues.... (Joseph D'Andrea 2000)
>At 4:45 PM 5/4/00, JHowarth@smithmicro.com wrote: >>I apologize for my incomplete answer before. >> >>Use [encrypt] without a seed value. The text will be encrypted the same way >>every time, so the compare will work. >> >>Thanks Ken for pointing out that seeded encrypted values are not always the >>same. Which is why some times his encrypt/decrypts do not work. > >No no no... Granted (no pun intended) that the encrypted values are >different each time through the results page, but when decrypted they >should yield the same result. > >[encrypt seed=joe]123[/encrypt] might yield bbbbb >and >[encrypt seed=joe]123[/encrypt] might yield xxxxx >and >[encrypt seed=joe]123[/encrypt] might yield yyyyy > >then > >[decrypt seed=joe]yyyyy[/decrypt] should yield 123 >[decrypt seed=joe]xxxxx[/decrypt] should yield 123 >[decrypt seed=joe]bbbbb[/decrypt] should yield 123 > >You see we don't really store the encrypted value, we're just >encrypting it to pass it in a URL. We use the decrypted value as the >key into the database to retreive the record. > >so my link looks like: > >[url][encrypt seed=joe][memberid][/encrypt][/url]> > > >then on the display.tpl page I have: > >[search..... &eqMEMBERIDdatarq=[unurl][decrypt >seed=joe][who][/decrypt][/unurl]] > >Help? Well let's see ... yes, it looks like you've urled the value after you've encrypted it, which makes sense -- but that only means you have to remember to unurl it BEFORE you try to decrypt it, not afterwards.And since you're using the decrypted value in a search context, you had better be sure to url the decrypted value, to be sure it doesn't have any & characters in it which would screw p your search string.Why don't you try this, I think it will work just fine:[search..... &eqMEMBERIDdatarq=[url][decrypt seed=joe][unurl][who][/unurl][/decrypt][/url]] ================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- 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 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:

[delete] problem (1997) Rotating Banners ... (was LinkExchange) (1997) Auto entering Friday's date in a field (2002) So what ya working on? (or have you completed?) (2004) credit card (1997) removelineitems (2000) [searchString] (1997) Some ThankYou page problems (1997) WebCat2 Append problem (B14Macacgi) (1997) [WriteFile] problems (1997) REPOST: The old multiple selection bit (2000) Hiding HTML and page breaks (1997) all records returned. (1997) browser info.txt and SSL (1997) pdf files? (2001) Signal Raised (1997) Multiple Newcarts (1996) Re:Authenticate (1998) mapping fields between databases (2001) Database cloning, or possible hack? (2003)