Re: decrypt trouble - solved
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 67018
interpreted = N
texte = Jim Ziegler wrote: >> You have your unurl and decrypt switched around me thinks. >> >> [unurl][decrypt seed=1234567][information][/decrypt][/unurl] >> > I tried it that way, and it failed to decrypt in certain fields/ > records. However, that got me thinking, and I tried this: > > [unurl][decrypt seed=1234567][unurl][information][/unurl][/decrypt][/ > unurl] > > So far it's working perfectly. I haven't found a single null character, > and everything decrypts fine. > Thanks for the inspiration, Donovan! > Jim Ziegler Jim,.. since I'm about to do this once again... :-) Your post got me confused.. btw, glad you got it solved... I always thought it was a dbl url encrypt and single unurl decrypt. But, it has been a while so I went looking in the archives. Here is what Scott has to say about it: **************************************** Single [URL]ing encrypted data is often not enough. Certain sequences = of [URL]ized random characters can still cause parse errors when the = data is passed in the query string (or retrieved from a db file) and = [UnUrl]ed. So it is a good practice to always double URL your encrypted = string. I.E.
[encrypt = seed=3D1664][source][/encrypt][/url][/url] Now here is where may get confusing for those who have not used the = [encryption]/[decryption] contexts very often... After the encrypted string has been [URL]ed twice, decrypting the string = may only require a SINGLE [UnURL] action. This is because an 'implicit' = [UnURL] may have already occurred when retrieving the encrypted data. = For example, when the encrypted data is retrieved from an HTTP form post = (or QueryString), or when the encrypted data is retrieved from a = database. Given this information, your test template should contain something like this: [url][url][encrypt seed=3D1664][source][/encrypt][/url][/url] [decrypt seed=3D1664][unurl][encr][/unurl][/decrypt] [url][url][encrypt seed=3D1664][decr][/encrypt][/url][/url] [decrypt seed=3D1664][unurl][unurl][encr][/unurl][/unurl][/decrypt] **************************************** Now, after reading Scotts post, I'm a bit more confused. His example doesn't follow the innate logic of tag based syntax from what I can tell... For example, here is a way to present a code in a browser exactly as written: [input][raw] --CODE-- [/raw][/input]
This code will not work if written as: [input][raw] --CODE--
[/raw][/input] Well, thats not exactly apples and apples but why wouldn't you use URL's in the same relative sequence as they were used going in.. ie: [url][url][encrypt seed=xxxx][/encrypt][/url][/url] then: [unurl][decrypt seed=xxxx][/decrypt][/unurl] (using only one [unurl][/unurl] since there is one implied) ??? Donovan -- =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o DONOVAN D. BROOKE EUCA Design Center <- Web Development (specializing in eCommerce),-> <- Custom Paint, Labels, and Specialty Signage. -> <- Home and Business Embellishment/Fabrication, -> <- Glass Blowing, and Art Glass -> PH/FAX:> 1 (608) 835-2476 Web:> http://www.egg.bz | http://www.euca.us =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o ------------------------------------------------------------- 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:
Jim Ziegler wrote: >> You have your unurl and decrypt switched around me thinks. >> >> [unurl][decrypt seed=1234567][information][/decrypt][/unurl] >> > I tried it that way, and it failed to decrypt in certain fields/ > records. However, that got me thinking, and I tried this: > > [unurl][decrypt seed=1234567][unurl][information][/unurl][/decrypt][/ > unurl] > > So far it's working perfectly. I haven't found a single null character, > and everything decrypts fine. > Thanks for the inspiration, Donovan! > Jim Ziegler Jim,.. since I'm about to do this once again... :-) Your post got me confused.. btw, glad you got it solved... I always thought it was a dbl url encrypt and single unurl decrypt. But, it has been a while so I went looking in the archives. Here is what Scott has to say about it: **************************************** Single [url]ing encrypted data is often not enough. Certain sequences = of [url]ized random characters can still cause parse errors when the = data is passed in the query string (or retrieved from a db file) and = [unurl]ed. So it is a good practice to always double URL your encrypted = string. I.E. [encrypt = seed=3D1664][source][/encrypt][/url][/url] Now here is where may get confusing for those who have not used the = [encryption]/[decryption] contexts very often... After the encrypted string has been [url]ed twice, decrypting the string = may only require a SINGLE [unurl] action. This is because an 'implicit' = [unurl] may have already occurred when retrieving the encrypted data. = For example, when the encrypted data is retrieved from an HTTP form post = (or QueryString), or when the encrypted data is retrieved from a = database. Given this information, your test template should contain something like this: [url][url][encrypt seed=3D1664][source][/encrypt][/url][/url] [decrypt seed=3D1664][unurl][encr][/unurl][/decrypt] [url][url][encrypt seed=3D1664][decr][/encrypt][/url][/url] [decrypt seed=3D1664][unurl][unurl][encr][/unurl][/unurl][/decrypt] **************************************** Now, after reading Scotts post, I'm a bit more confused. His example doesn't follow the innate logic of tag based syntax from what I can tell... For example, here is a way to present a code in a browser exactly as written: [input][raw] --CODE-- [/raw][/input]
This code will not work if written as: [input][raw] --CODE--
[/raw][/input] Well, thats not exactly apples and apples but why wouldn't you use URL's in the same relative sequence as they were used going in.. ie: [url][url][encrypt seed=xxxx][/encrypt][/url][/url] then: [unurl][decrypt seed=xxxx][/decrypt][/unurl] (using only one [unurl][/unurl] since there is one implied) ??? Donovan -- =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o DONOVAN D. BROOKE EUCA Design Center <- Web Development (specializing in eCommerce),-> <- Custom Paint, Labels, and Specialty Signage. -> <- Home and Business Embellishment/Fabrication, -> <- Glass Blowing, and Art Glass -> PH/FAX:> 1 (608) 835-2476 Web:> http://www.egg.bz | http://www.euca.us =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o ------------------------------------------------------------- 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/
Donovan Brooke
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:
Pieces Show Up! Curse You! (2000)
WebCatalog2 Feature Feedback (1996)
WebCat2b15MacPlugin - showing [math] (1997)
problem: search crashes webstar (1997)
[WebDNA] Upgrade 4.5.1 to 6.0a (2009)
Re[2]: Re[2]: running WebCatalog under Apache on NT? (2000)
Webcatalog server support (1997)
Remove from list server (1997)
Line items in table cells (1997)
WCS Newbie question (1997)
WebCat2b13MacPlugIn - More limits on [include] (1997)
multi-paragraph fields (1997)
Webcatalog [blank] Problem (1999)
[FEATURE REQUEST] (2004)
WCS Newbie question (1997)
converting tabs (1997)
Using ticks (2000)
ShippingCosts (1998)
range searching (1998)
spaces in [texta] (1998)