We store ours in a CF struct:
DSN = StructNew();
DSN.Source =
DSN.Username =
DSN.Password =
And then we use that in the queries. We put that in a file that starts with
an _ and then we deny any access to files that start with an _ so people
can access it by some means.
My boss is a stickler
Ben, Thanks for the suggestion! Are you restricting the file access at the web
server level, or in CF? If in CF, are you testing for the file name in CGI
scope to deny access?
We store ours in a CF struct:
DSN = StructNew();
DSN.Source =
DSN.Username =
DSN.Password =
And then we use that
for Pedro
-Original Message-
From: Stan Winchester [mailto:[EMAIL PROTECTED]
Sent: Friday, December 16, 2005 8:32 AM
To: CF-Talk
Subject: Re: Required DSN Username Password
Ben, Thanks for the suggestion! Are you restricting the file access at the
web server level, or in CF? If in CF
212.691.3477 fax
www.nylontechnology.com
Vote for Pedro
-Original Message-
From: Stan Winchester [mailto:[EMAIL PROTECTED]
Sent: Friday, December 16, 2005 8:32 AM
To: CF-Talk
Subject: Re: Required DSN Username Password
Ben, Thanks for the suggestion! Are you restricting the file access
I think the idea behind doing this sort of thing (requiring U P in
the code) is its easier to hack the CF stuff -- which often resides in
a known location, for example -- than it is to get at the templates
themselves. And if they get at the templates you're through anyway.
One thing I make a
I also like to setup restrict data sources. I don't like having the user name
password on the server. I hope the system I have shown is acceptable.
Fortunately accessing a cfc directly through a browser throws a 403 error in
IIS, and ftp requires authenication.
Matt, I see by your title you
6 matches
Mail list logo