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:
>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
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...