Re: [WebDNA] Encode cookies ONLY via "method=Base64"
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 101276
interpreted = N
texte = Ken couldn't you do the math work in a shell or dos script and then encrypt based on the result?On Oct 27, 2008, at 9:11 PM, Kenneth Grome wrote:> Hi Matthew,>> I tested WebDNA and learned that it won't produce [math]> results more than 15 chars long before it resorts to> scientific notation, and therefore it appears your> suggestion is not possible ... :(>> I also did a bunch of reading online about prime numbers> (very interesting) but none of it matters for use in WebDNA> if the [math] context cannot produce numbers more than 15> chars long.>> It sure would be nice if encrypt / decrypt worked with> cookies, and I'm not sure why it doesn't when it works with> db's. Any theories about this?>> Sincerely,> Ken Grome>>>>>>>> Yes the 533000389 is a prime number. Do a Google search>> for prime numbers and you should fine many sources>> online. Just pick a favorite number to use on your own.>> I would suggest something 9 or more digits long.>>>> The 40 in my equation was simply part of the example. 10>> characters for the user name, 10 characters for the>> password. Concatenate them together and you have 20>> characters. Assuming you use 2 digit numbers in your>> ascii conversion table these 20 characters would convert>> to a 40 digit number.>>>> The number 125 was just a random number I pulled from>> thin air simply to add another multiplier into the>> equation. But you can create any equation you want.>>>> Just to make sure everyone is following here's what I'm>> suggesting for the ascii table:>> A=24>> B=37>> C=74>> D=82>> E=90>> F=64>> G=83>> H=71>> *WARNING* make sure you use numbers greater than 9 or>> this method will fail.>>>> So then if you are converting the username ABAB and the>> password DFGH you would end up with:>> ABABDFGH = 2437243782648371>> That would be the number you then encode with your prime>> number.> ---------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list
.> To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us> old archives: http://dev.webdna.us/TalkListArchive/Robert MinorDirector of Internet Services------------------------------------------------------------Cybermill Communicationshttp://www.cybermill.com http://www.merchantmaker.comProviding Ecommerce and interactive website development andhosting services on Macintosh, Windows NT, *nix, and AS/400.Complete ddos proof hosting solutions and network services.
Associated Messages, from the most recent to the oldest:
Ken couldn't you do the math work in a shell or dos script and then encrypt based on the result?On Oct 27, 2008, at 9:11 PM, Kenneth Grome wrote:> Hi Matthew,>> I tested WebDNA and learned that it won't produce [math]> results more than 15 chars long before it resorts to> scientific notation, and therefore it appears your> suggestion is not possible ... :(>> I also did a bunch of reading online about prime numbers> (very interesting) but none of it matters for use in WebDNA> if the [math] context cannot produce numbers more than 15> chars long.>> It sure would be nice if encrypt / decrypt worked with> cookies, and I'm not sure why it doesn't when it works with> db's. Any theories about this?>> Sincerely,> Ken Grome>>>>>>>> Yes the 533000389 is a prime number. Do a Google search>> for prime numbers and you should fine many sources>> online. Just pick a favorite number to use on your own.>> I would suggest something 9 or more digits long.>>>> The 40 in my equation was simply part of the example. 10>> characters for the user name, 10 characters for the>> password. Concatenate them together and you have 20>> characters. Assuming you use 2 digit numbers in your>> ascii conversion table these 20 characters would convert>> to a 40 digit number.>>>> The number 125 was just a random number I pulled from>> thin air simply to add another multiplier into the>> equation. But you can create any equation you want.>>>> Just to make sure everyone is following here's what I'm>> suggesting for the ascii table:>> A=24>> B=37>> C=74>> D=82>> E=90>> F=64>> G=83>> H=71>> *WARNING* make sure you use numbers greater than 9 or>> this method will fail.>>>> So then if you are converting the username ABAB and the>> password DFGH you would end up with:>> ABABDFGH = 2437243782648371>> That would be the number you then encode with your prime>> number.> ---------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list .> To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us> old archives: http://dev.webdna.us/TalkListArchive/Robert MinorDirector of Internet Services------------------------------------------------------------Cybermill Communicationshttp://www.cybermill.com http://www.merchantmaker.comProviding Ecommerce and interactive website development andhosting services on Macintosh, Windows NT, *nix, and AS/400.Complete ddos proof hosting solutions and network services.
Bob Minor
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:
[WebDNA] Small Parsing Problem (2009)
Running 2 two WebCatalog.acgi's (1996)
WebCat2b15MacPlugin - showing [math] (1997)
HELP! 10K hits per hour for pages that no longer exist! (2000)
re:check boxes (1997)
WebCatalog can't find database (1997)
docs for WebCatalog2 (1997)
Single Link browsing (1997)
new storefront (2003)
setting taxable to true (1997)
Converting Quotes in Javascript (2001)
[shipTotal] or [shippingTotal] ??? (1998)
two unique banners on one page (1997)
Page Breaks (1999)
unable to launch acgi in WebCat (1997)
2nd WebCatalog2 Feature Request (1996)
Fun with dates (1997)
Orders coming up blank (2004)
[OT] CSS and SSI books (2004)
Physical Proximity searches (2000)