Re: [WebDNA] Encode cookies ONLY via "method=Base64"

This WebDNA talk-list message is from

2008


It keeps the original formatting.
numero = 101278
interpreted = N
texte = This is a multi-part message in MIME format. --------------050803010908080300080706 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Oh well. I've never had a need to calculate in webdna more than 15 characters. That's why I asked in the beginning of my post if it could calculate that high. However, thinking further out of the hat here, you could still use the same method, just use a smaller prime number and instead of starting with a 40 digit number, break it down into manageable segments, do the calculations, then concatenate it back together again. I still feel that a mathematical approach is much faster than anything anyone can put together with databases or tables. Matthew A Perosi JewelerWebsites.com ------------------------------by Psi Prime------- Senior Web Developer 323 Union Blvd. Totowa, NJ 07512 Pre-Sales: 888.872.0274 Service: 973.413.8213 Training: 973.413.8214 Fax: 973.413.8217 http://www.jewelerwebsites.com http://en.wikipedia.org/wiki/Psi_Prime%2C_Inc http://www.psiprime.com 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/ > > > --------------050803010908080300080706 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Oh well.
I've never had a need to calculate in webdna more than 15 characters.=C2=A0 That's why I asked in the beginning of my post if it could calculate that high.

However, thinking further out of the hat here, you could still use the same method, just use a smaller prime number and instead of starting with a 40 digit number, break it down into manageable segments, do the calculations, then concatenate it back together again.

I still feel that a mathematical approach is much faster than anything anyone can put together with databases or tables.
Matthew A Perosi            Jewe=lerWebsites.com------------------------------by Psi Prime-------Senior Web Developer             323 Union Blvd.                                 Totowa, NJ 07512Pre-Sales: 888.872.0274Service:   973.413.8213Training:  973.413.8214Fax:       973.413.8217http://www.jewelerwebsites.comhttp://en.wikipedia.org/wiki/Psi_Prime%2C_Inchttp:=//www.psiprime.com


Kenneth Grome wrote: 
Hi Matthew,I tested WebDNA and learned that it won't produce [math]=20results more than 15 chars long before it resorts to=20scientific notation, and therefore it appears your=20suggestion is not possible ... :(I also did a bunch of reading online about prime numbers=20(very interesting) but none of it matters for use in WebDNA=20if the [math] context cannot produce numbers more than 15=20chars long.It sure would be nice if encrypt / decrypt worked with=20cookies, and I'm not sure why it doesn't when it works with=20db's.  Any theories about this?Sincerely,Ken Grome  
Yes the 533000389 is a prime number.  Do a Google sear=chfor prime numbers and you should fine many sourcesonline.  Just pick a favorite number to use on your own.=20I would suggest something 9 or more digits long.The 40 in my equation was simply part of the example.  10characters for the user name, 10 characters for thepassword.  Concatenate them together and you have 20characters.  Assuming you use 2 digit numbers in yourascii conversion table these 20 characters would convertto a 40 digit number.The number 125 was just a random number I pulled fromthin air simply to add another multiplier into theequation.  But you can create any equation you want.Just to make sure everyone is following here's what I'msuggesting for the ascii table:A=3D24B=3D37C=3D74D=3D82E=3D90F=3D64G=3D83H=3D71*WARNING* make sure you use numbers greater than 9 orthis method will fail.So then if you are converting the username ABAB and thepassword DFGH you would end up with:ABABDFGH =3D 2437243782648371That would be the number you then encode with your primenumber.    
-------------------------------------------------=--------This message is sent to you because you are subscribed tothe mailing list <talk@webdna.us>.To unsubscribe, E-mail to: <talk-leave@webdna.us>archives: http://mail.webdna.us/list/talk@webdna.usold archives: http://dev.webdna.us/TalkListArchive/
--------------050803010908080300080706-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Stuart Tremain 2012)
  2. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Brian Fries 2012)
  3. Re: [WebDNA] Encode cookies ONLY via "method=Base64" ("Psi Prime Inc, Matthew A Perosi " 2012)
  4. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Govinda 2012)
  5. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Stuart Tremain 2012)
  6. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Donovan Brooke 2008)
  7. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  8. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  9. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Donovan Brooke 2008)
  10. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  11. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Donovan Brooke 2008)
  12. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  13. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Donovan Brooke 2008)
  14. Re: [WebDNA] Encode cookies ONLY via "method=Base64" ("Gary Krockover" 2008)
  15. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Donovan Brooke 2008)
  16. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Donovan Brooke 2008)
  17. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Marc Thompson 2008)
  18. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Bob Minor 2008)
  19. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Brian Fries 2008)
  20. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Marc Thompson 2008)
  21. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Patrick McCormick 2008)
  22. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  23. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Brian Fries 2008)
  24. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Christer Olsson 2008)
  25. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  26. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Donovan Brooke 2008)
  27. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  28. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  29. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  30. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  31. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  32. Re: [WebDNA] Encode cookies ONLY via "method=Base64" ("Psi Prime, Matthew A Perosi " 2008)
  33. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Stuart Tremain 2008)
  34. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Bob Minor 2008)
  35. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  36. RE: [WebDNA] Encode cookies ONLY via "method=Base64" ("Olin Lagon" 2008)
  37. RE: [WebDNA] Encode cookies ONLY via "method=Base64" ("Olin Lagon" 2008)
  38. Re: [WebDNA] Encode cookies ONLY via "method=Base64" ("Psi Prime, Matthew A Perosi " 2008)
  39. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  40. Re: [WebDNA] Encode cookies ONLY via "method=Base64" ("Psi Prime, Matthew A Perosi " 2008)
  41. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  42. Re: [WebDNA] Encode cookies ONLY via "method=Base64" ("Psi Prime, Matthew A Perosi " 2008)
  43. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  44. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Stuart Tremain 2008)
  45. [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
This is a multi-part message in MIME format. --------------050803010908080300080706 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Oh well. I've never had a need to calculate in webdna more than 15 characters. That's why I asked in the beginning of my post if it could calculate that high. However, thinking further out of the hat here, you could still use the same method, just use a smaller prime number and instead of starting with a 40 digit number, break it down into manageable segments, do the calculations, then concatenate it back together again. I still feel that a mathematical approach is much faster than anything anyone can put together with databases or tables. Matthew A Perosi JewelerWebsites.com ------------------------------by Psi Prime------- Senior Web Developer 323 Union Blvd. Totowa, NJ 07512 Pre-Sales: 888.872.0274 Service: 973.413.8213 Training: 973.413.8214 Fax: 973.413.8217 http://www.jewelerwebsites.com http://en.wikipedia.org/wiki/Psi_Prime%2C_Inc http://www.psiprime.com 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/ > > > --------------050803010908080300080706 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Oh well.
I've never had a need to calculate in webdna more than 15 characters.=C2=A0 That's why I asked in the beginning of my post if it could calculate that high.

However, thinking further out of the hat here, you could still use the same method, just use a smaller prime number and instead of starting with a 40 digit number, break it down into manageable segments, do the calculations, then concatenate it back together again.

I still feel that a mathematical approach is much faster than anything anyone can put together with databases or tables.
Matthew A Perosi            Jewe=lerWebsites.com------------------------------by Psi Prime-------Senior Web Developer             323 Union Blvd.                                 Totowa, NJ 07512Pre-Sales: 888.872.0274Service:   973.413.8213Training:  973.413.8214Fax:       973.413.8217http://www.jewelerwebsites.comhttp://en.wikipedia.org/wiki/Psi_Prime%2C_Inchttp:=//www.psiprime.com


Kenneth Grome wrote: 
Hi Matthew,I tested WebDNA and learned that it won't produce [math]=20results more than 15 chars long before it resorts to=20scientific notation, and therefore it appears your=20suggestion is not possible ... :(I also did a bunch of reading online about prime numbers=20(very interesting) but none of it matters for use in WebDNA=20if the [math] context cannot produce numbers more than 15=20chars long.It sure would be nice if encrypt / decrypt worked with=20cookies, and I'm not sure why it doesn't when it works with=20db's.  Any theories about this?Sincerely,Ken Grome  
Yes the 533000389 is a prime number.  Do a Google sear=chfor prime numbers and you should fine many sourcesonline.  Just pick a favorite number to use on your own.=20I would suggest something 9 or more digits long.The 40 in my equation was simply part of the example.  10characters for the user name, 10 characters for thepassword.  Concatenate them together and you have 20characters.  Assuming you use 2 digit numbers in yourascii conversion table these 20 characters would convertto a 40 digit number.The number 125 was just a random number I pulled fromthin air simply to add another multiplier into theequation.  But you can create any equation you want.Just to make sure everyone is following here's what I'msuggesting for the ascii table:A=3D24B=3D37C=3D74D=3D82E=3D90F=3D64G=3D83H=3D71*WARNING* make sure you use numbers greater than 9 orthis method will fail.So then if you are converting the username ABAB and thepassword DFGH you would end up with:ABABDFGH =3D 2437243782648371That would be the number you then encode with your primenumber.    
-------------------------------------------------=--------This message is sent to you because you are subscribed tothe mailing list <talk@webdna.us>.To unsubscribe, E-mail to: <talk-leave@webdna.us>archives: http://mail.webdna.us/list/talk@webdna.usold archives: http://dev.webdna.us/TalkListArchive/
--------------050803010908080300080706-- "Psi Prime, Matthew A Perosi "

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:

Shell scripts with sudoer (2004) Ok here is a question? (1997) Users.db (1998) Email Mac (2002) Nested tags count question (1997) Grouping search fields, etc. (1997) Cart doesn't interpret tag! (1997) back button loses cart (update for ken) (2000) Include a big block of text (1997) Re[2]: Support suggestions - long (was politeness, et al) (2000) TIP OF THE DAY quick & dirty html text (2004) bug in [SendMail] (1997) Frames and WebCat (1997) ShowIf helper? (1998) FYI: virus alert (1996) Linux/webcat points (2000) Commitdatabase tag (1998) Writefile (2000) Getting total number of items ordered (1997) Hiding Brands (2004)