Re: Making a secret cookie code in WebCat

This WebDNA talk-list message is from

2001


It keeps the original formatting.
numero = 39143
interpreted = N
texte = >Hi all, > >I am thinking of redefining the way I make Cookies on my WebSTAR/WebCatalog >solution. > >The thingy I'm really looking for is for WebCatalog to make a Cookie Value, >which is unique and not readable. > >So the cookie should not be e.g.. > >20011014210005 >YYYYMMDDHHMMSS > >But rather something totally useless for the normal user, which initially >can view the Cookie in the browser. > >Any other ideas on how to make more secure session Cookies using WebCat is >welcome too. Here is a simple thought.Start with Cart or Date i.e., 20011014210005 Then do a convertchars on it with a custom database The custom database could be as simple as:from to 0 a 1 b 2 c etc.Mix it up for randomness to your delight.This will allow you to keep using the cart/date generated session id but convert it to a human un-readable token.The only thing you are adding is the random look to the id. Cart is just as good but simply numerical. -- Sam LewisSamLewis.com Tel: 626-852-0956 Fax: 916-404-5698------------------------------------------------------------- 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://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Making a secret cookie code in WebCat (Bob Minor 2001)
  2. Re: Making a secret cookie code in WebCat (Sam Lewis 2001)
  3. Re: Making a secret cookie code in WebCat (John Peacock 2001)
  4. Making a secret cookie code in WebCat (Palle B. Nielsen (PowerPalle) 2001)
>Hi all, > >I am thinking of redefining the way I make Cookies on my WebSTAR/WebCatalog >solution. > >The thingy I'm really looking for is for WebCatalog to make a Cookie Value, >which is unique and not readable. > >So the cookie should not be e.g.. > >20011014210005 >YYYYMMDDHHMMSS > >But rather something totally useless for the normal user, which initially >can view the Cookie in the browser. > >Any other ideas on how to make more secure session Cookies using WebCat is >welcome too. Here is a simple thought.Start with Cart or Date i.e., 20011014210005 Then do a convertchars on it with a custom database The custom database could be as simple as:from to 0 a 1 b 2 c etc.Mix it up for randomness to your delight.This will allow you to keep using the cart/date generated session id but convert it to a human un-readable token.The only thing you are adding is the random look to the id. Cart is just as good but simply numerical. -- Sam LewisSamLewis.com Tel: 626-852-0956 Fax: 916-404-5698------------------------------------------------------------- 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://search.smithmicro.com/ Sam Lewis

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] Successful, working WebDNA7/CentOS install? (2013) Encrypt broken on Mac 3.05b13?? (2000) users.db (1999) Changing SubTotal (2003) Looking for a host (1997) SQL connection (2000) Undeliverable Mail (1997) ODBC-Interface (2000) emailer and other smtp (1998) pretty Urgent: Crash after addlineitem (2001) flushdatabases (1997) Firesite and [referrer] atg broke (1997) [showif] results returned... (2003) [WebDNA] Installing WebDNA on Windows 7 64 Bit, Home Premium (2010) test (2006) Seeking WebCat Bulletin Board (1999) carriage returns in data (1997) cc auth with [purchase] (1998) [WebDNA] WebDNA 7 (2011) Errata: WCS Newbie question (1997)