Re: Ken's Data Manager (finally available I think ...)

This WebDNA talk-list message is from

2005


It keeps the original formatting.
numero = 61351
interpreted = N
texte = Ken, I would caution against a fixed, unchangeable password. Passwords can get compromised, or need to be changed for a number of legitimate reasons. Then you're stuck having to do it for them. Perhaps let the password be changed, but keep the username fixed, if it's an exclusive license thing. Terry >>It's a little dangerous leaving it in a directory with >>a default user/pass and no ability to change them. > >Agreed. The code in the kdm.tpl is possibly going to be part of a >commercial product, that's why this one is encrypted with the >default user/pass value. When I sell licenses I will probably set >the user/pass values individually for each copy sold, depending upon >what the owner wants for those values. > >Sincerely, >Kenneth Grome >www.kengrome.com ------------------------------------------------------------- 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://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Ken's Data Manager (finally available I think ...) ( Kenneth Grome 2005)
  2. Re: Ken's Data Manager (finally available I think ...) ( Terry Wilson 2005)
  3. Re: Ken's Data Manager (finally available I think ...) ( Kenneth Grome 2005)
  4. Re: Ken's Data Manager (finally available I think ...) ( Lester 2005)
  5. Re: Ken's Data Manager (finally available I think ...) ( Lester 2005)
  6. Re: Ken's Data Manager (finally available I think ...) ( Gary Krockover 2005)
  7. Re: Ken's Data Manager (finally available I think ...) ( Gary Krockover 2005)
  8. Re: Ken's Data Manager (finally available I think ...) ( Lester 2005)
  9. Re: Ken's Data Manager (finally available I think ...) ( Lester 2005)
  10. Ken's Data Manager (finally available I think ...) ( Kenneth Grome 2005)
Ken, I would caution against a fixed, unchangeable password. Passwords can get compromised, or need to be changed for a number of legitimate reasons. Then you're stuck having to do it for them. Perhaps let the password be changed, but keep the username fixed, if it's an exclusive license thing. Terry >>It's a little dangerous leaving it in a directory with >>a default user/pass and no ability to change them. > >Agreed. The code in the kdm.tpl is possibly going to be part of a >commercial product, that's why this one is encrypted with the >default user/pass value. When I sell licenses I will probably set >the user/pass values individually for each copy sold, depending upon >what the owner wants for those values. > >Sincerely, >Kenneth Grome >www.kengrome.com ------------------------------------------------------------- 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://webdna.smithmicro.com/ Terry Wilson

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:

How to pass from a detail page to another? (1998) Errata: WCS Newbie question (1997) webCatalog and Stocks (1998) Alternating BGColors in Table Rows (1998) WebCat2 - Getting to the browser's username/password data (1997) HTML text cannot be copied to clipboard? (1999) Targeting [redirect] to a frame? (1998) A little help on e-mail (HELP!!! :-) ) (1998) PIXO (1997) Time code! (2002) WCS Newbie question (1997) Setting a null value for reply to address using sendmail... (2001) [BoldWords] WebCat.acgib15Mac (1997) [WebDNA] [raw] tag with [interpret] question (2010) flushing databases (2003) Problems getting parameters passed into email. (1997) Hiding a subsection of text (2002) [WebDNA] making all fields on a form mandatory (2013) Setting up shop (1997) Configuration Q (1998)