Tally List : mailing list management, archiving, and analysis
click for archive home
 
Archive of:
Fusebox
Cold Fusion Fuse Box List
 
home
24 hour view
quick stats
weekly updates
 
all tallylists
corporate solutions
archive your favorite
help / feedback


Search the Tallylist search by keyword:

About CF Fusebox Methods :
product's home
product's list home
 
  Archived TallyList / Fusebox: 
Subject: RE: Managing program flow
McCollough, Alan (150p/+0r)     Posted: Monday 07 May 2001
This post: 64 views, +0 rating

As far as I can tell, the ONLY thing you should ever need to pass is the cftoken. Take the hit on the webserver/SQL server. Think of it as a lockbox with a key. You keep the box, yet give each client a unique key, the cftoken.

All you need is a decent cftoken. Do the reg hack (that's for you Windows folks) to add in the UuidToken = 1 key to HKEY_LOCAL_MACHINE\Allaire\ColdFusing\CurrentVersion\Clients. Then if you are using db-driven client vars, manually change the size of the CFID fields in the client variable database to 50, and yer set. Now your clients get a UUID for their CFTOKEN.

You've got a good key for each client, so why would you need to pass anything back to 'em? Performance? Feh. Go for security. Remember the correction officer's mantra, "Security is not Convenient".

> -----Original Message----- > From: Nat Papovich [SMTP:nat@webthugs.com] > Sent: Monday, May 07, 2001 6:52 AM > To: Fusebox > Subject: RE: Managing program flow > > Right, but I would argue that it is safe to store only the productID, not > the price, and calculate the price each time the display of it is needed > by > hitting the DB. Passing checkout information in hidden form fields CAN be > secure, as long as you pass insecure data, not things like CC info, price, > tax info, etc. > > NAT > > > -----Original Message----- > > From: amittalwar@intellikaps.com [mailto:amittalwar@intellikaps.com] > > Sent: Monday, May 07, 2001 4:46 AM > > To: Fusebox > > Subject: RE: Managing program flow > > > > > > That wasn't my point. My point was the concept rather than the > > impementation > > attribute. > > Check out www.bratcatalog.com > > they do use hidden fields to store data and not at all secure. > > Amit Talwar > > Intellikaps > > > > -----Original Message----- > > From: Nat Papovich [mailto:nat@webthugs.com] > > Sent: Monday, May 07, 2001 9:52 AM > > To: Fusebox > > Subject: RE: Managing program flow > > > > > > Erik is smart enough to either not store price info in a form field or > to > > check that price matches price for productID on order submission. > > > > > -----Original Message----- > > > From: BORKMAN Lee [mailto:lee_Borkman@rta.nsw.gov.au] > > > Sent: Sunday, May 06, 2001 6:11 PM > > > To: Fusebox > > > Subject: RE: Managing program flow > > > > > > > > > Yes, but you can possibly live with hidden fields as long as you > always > > > check for a trusted referer. > > > > > > -----Original Message----- > > > From: amittalwar@intellikaps.com [mailto:amittalwar@intellikaps.com] > > > > > > > > > Hi, > > > Well Erik It is Absoloutely going cause security hazards if you > > are using > > > hidden varables in your page. > > > > > > Conside this, for example you store price of a product as a hidden > > > variable. Now if the users saves the page to his system and reduces > the > > > price and then submits the page you will never know that the price is > > > correct or incorrect as there will be no cross check with the > > price in the > > > database. > > > > > > > > > IMPORTANT NOTICE: > > > This e-mail and any attachment to it is intended only to be read > > > or used by > > > the named addressee. It is confidential and may contain legally > > > privileged > > > information. No confidentiality or privilege is waived or lost by any > > > mistaken transmission to you. If you receive this e-mail in > > error, please > > > immediately delete it from your system and notify the sender. > > > You must not > > > disclose, copy or use any part of this e-mail if you are not > > the intended > > > recipient. The RTA is not responsible for any unauthorised > > alterations to > > > this e-mail or attachment to it. > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/fusebox@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists


Similar Subject Line Posts (+/- two weeks of this post)
RE: Managing program flow  07 May 2001   (61 v/ +0 r)
RE: Managing program flow  07 May 2001   (64 v/ +0 r)
RE: Managing program flow  07 May 2001   (56 v/ +0 r)
RE: Managing program flow  07 May 2001   (59 v/ +0 r)
RE: Managing program flow  07 May 2001 (this post)   (64 v/ +0 r)
RE: Managing program flow  07 May 2001   (60 v/ +0 r)
RE: Managing program flow  07 May 2001   (66 v/ +0 r)
RE: Managing program flow  07 May 2001   (53 v/ +0 r)
RE: Managing program flow  07 May 2001   (51 v/ +0 r)
RE: Managing program flow  06 May 2001   (58 v/ +0 r)
RE: Managing program flow  06 May 2001   (67 v/ +0 r)
RE: Managing program flow  06 May 2001   (61 v/ +0 r)
Re: Managing program flow  06 May 2001   (58 v/ +0 r)
RE: Managing program flow  05 May 2001   (49 v/ +0 r)
RE: Managing program flow  04 May 2001   (59 v/ +0 r)
RE: Managing program flow  04 May 2001   (62 v/ +0 r)
RE: Managing program flow  04 May 2001   (58 v/ +0 r)
Re: Managing program flow  04 May 2001   (56 v/ +0 r)
RE: Saving form variables in WDDX (Was: Managing program flow)  04 May 2001   (53 v/ +0 r)
RE: Saving form variables in WDDX (Was: Managing program flow)  04 May 2001   (46 v/ +0 r)
Saving form variables in WDDX (Was: Managing program flow)  04 May 2001   (53 v/ +0 r)
Re: Managing program flow  03 May 2001   (55 v/ +0 r)
Re: Managing program flow  03 May 2001   (58 v/ +0 r)
Re: Managing program flow  03 May 2001   (72 v/ +0 r)
RE: RE: Managing program flow  03 May 2001   (53 v/ +0 r)
 

Send a reply to the Fusebox list!
click to send a reply! NOTE: Many lists will reject your post unless you have already registered with them. Also - don't forget the right account to send from (for those with multiple emails!)

Feedback: If this post was exceptionally helpful, please help by giving this post a positive review.

 

TallyList : copyright Ububik - 2000