Re: Hiding Contexts

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 36458
interpreted = N
texte = >I'm a real newbie to WebDNA and I'm having some trouble. I'm running >Typhoon Pro on OS9 on a G4/400.Which version? >. >What I have found is that someone with a little knowledge of HTML >can download the form, modify the client name and then gain access to >another client's account.Prevent this by requiring the referring page to come from your server, or by making the visitor login with a username and password that you store in the users.db, or by other similar methods ... >I first thought that this could be solved with encrypting the template, but >for some reason I cannot get this to work.Encrypting templates does nothing to change the HTML sent to the browser. The reason for encrypting your templates is to prevent people who have direct access to those templates from seeing your webdna code -- not to prevent the browser from receiving the proper HTML code. If you write a commercial solution that you want to sell, that's when you need to protect your templates. ================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- 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: Hiding Contexts (Peter Ostry 2000)
  2. Re: Hiding Contexts (John Butler 2000)
  3. Re: Hiding Contexts (Peter Ostry 2000)
  4. Re: Hiding Contexts (Kenneth Grome 2000)
  5. Hiding Contexts (Steve Dannaway 2000)
>I'm a real newbie to WebDNA and I'm having some trouble. I'm running >Typhoon Pro on OS9 on a G4/400.Which version? >. >What I have found is that someone with a little knowledge of HTML >can download the form, modify the client name and then gain access to >another client's account.Prevent this by requiring the referring page to come from your server, or by making the visitor login with a username and password that you store in the users.db, or by other similar methods ... >I first thought that this could be solved with encrypting the template, but >for some reason I cannot get this to work.Encrypting templates does nothing to change the HTML sent to the browser. The reason for encrypting your templates is to prevent people who have direct access to those templates from seeing your webdna code -- not to prevent the browser from receiving the proper HTML code. If you write a commercial solution that you want to sell, that's when you need to protect your templates. ================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- 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/ Kenneth Grome

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:

WebCat2 beta 11 - new prefs ... (1997) Forcing Paragraph Breaks on Results (1998) File Upload problem solved (2002) insert graphic in email (2000) Problem with version 4 browsers (1998) Webmerch Error (1998) Resume Catalog ? (1997) So many lookers, hey smith micro (2003) [WebDNA] [OT] Phone solution for multiple companies at same location (2010) two unique banners on one page (1997) Restart of DBserver (1997) Auto-closing of databases (was DON'T use old cart file!) (1997) Forbidden CGI Error (1997) autocommit problem (1998) [WebDNA] WebDNA Not Sending Email (2009) orderfile and setlineitems (1998) tricky embedded[showifs/hideifs] (w/ code.. long) (2000) [WebDNA] WebDNA installers (2015) Problems appending to database (1997) WebCat2 - Getting to the browser's username/password data (1997)