Re[2]: Re[3]: Problem with new formvariables

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 31227
interpreted = N
texte = Jesse - The only sensible level of security is one that you have to explicitly _opt out of_, not remember to enable. And the discussion at hand is not whether variables defined within a template could be locked, but rather whether variables passed as part of the command line could override variables on the template.i.e. index.shtml?ipaddress=10.0.0.1 currently overrides the system variable [ipaddress], which is _highly_ insecure. This can be rightly considered to be a bugfix, not an upgrade.John Peacock ____________________Reply Separator____________________ Subject: Re: Re[3]: Problem with new formvariables Author: Date: 5/2/2000 11:02 AMAre you saying that if you had:[text secure=t]SecureVar=T[/text] [text]Securevar=f[/text]that the value would get to F? but it would be secure.The only way to change secure vars should be:[text secure=t]securevar=t[/text] [text secure=t]securevar=f[/text] Jesse Proudman - NineWire Productions http://www.ninewire.com <-> jesse@ninewire.com Innovative and Creative Web Design and Hosting ############################################################# 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 To switch to the INDEX mode, E-mail to Send administrative queries to Associated Messages, from the most recent to the oldest:

    
  1. Re[2]: Re[3]: Problem with new formvariables (jpeacock@univpress.com 2000)
  2. Re[2]: Re[3]: Problem with new formvariables (jpeacock@univpress.com 2000)
  3. Re: Re[2]: Re[3]: Problem with new formvariables (Jesse Proudman 2000)
Jesse - The only sensible level of security is one that you have to explicitly _opt out of_, not remember to enable. And the discussion at hand is not whether variables defined within a template could be locked, but rather whether variables passed as part of the command line could override variables on the template.i.e. index.shtml?ipaddress=10.0.0.1 currently overrides the system variable [ipaddress], which is _highly_ insecure. This can be rightly considered to be a bugfix, not an upgrade.John Peacock ____________________Reply Separator____________________ Subject: Re: Re[3]: Problem with new formvariables Author: Date: 5/2/2000 11:02 AMAre you saying that if you had:[text secure=t]SecureVar=T[/text] [text]Securevar=f[/text]that the value would get to F? but it would be secure.The only way to change secure vars should be:[text secure=t]securevar=t[/text] [text secure=t]securevar=f[/text] Jesse Proudman - NineWire Productions http://www.ninewire.com <-> jesse@ninewire.com Innovative and Creative Web Design and Hosting ############################################################# 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 To switch to the INDEX mode, E-mail to Send administrative queries to jpeacock@univpress.com

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:

Claris HomePage messes up the code (1997) [WebDNA] JSONobject (2020) sendmail and accented characters (1998) Emailer again (1997) Why does WebCat do this? (2001) expired beta (1997) [AppendFile] problem (WebCat2b13 Mac .acgi) (1997) win2003 server (Web, standard, small business, edition) (2005) Date Formats (1997) AD Error Msg (1997) IE Cache Problems... (1999) Question re: FlushDatabases (1997) problem with NT beta (1997) [WebDNA] OAuth - anybody done this yet? (2009) Banners (1997) AAgghh!! Help, please. SSL strikes again. (1997) PCS Frames (1997) MacWEEK article help needed (1996) unique ascending numbers (2003) Showing specific [cart] contents (1998)