Which Is best - Fixed DSN or DSNLess??

[PaulSc]

Hi,
I wonder if I can ask for some advice please?

We develop all our ASP applications using DSNLess database connections and have now started to do this for a number of ColdFusion apps as well.

The end client has raised the question as to whether a DSNLess connection is 'safe' or 'safer' than a DSN setup on the server itself?

I know that the ASP/CF code is never sent to the client but is it possible to 'break' in if DSNLess connections are used?

Has anybody any comments on/experiences of this please that they may wish to share?

Thanks

PaulSc.

 

[onpnt]

dsn-less is faster and less resource usage
dsn is more secure

although there are plenty of ways to make the DB and files secure other then the dsn creation
eg:
directory locking (password protect)
DB settings etc...


_____________________________________________________________________
[sub]Where have all my friends gone to????[/sub]

http://www.onpntwebdesigns.com

 

[codestorm]

Why in DSN(-full ) more secure?

I would think it the work of 5 minutes to look into a DSN file/registry setting if the cracker had broken into your web server.

codestorm
Newbie Life Member.
Fire bad. Tree pretty. - Buffy
<insert witticism here>

 

[sindhufire]

I would like to vote for DSN-Less connections, bcoz it doesn't need to configure the DSN settings again and again.
DSN-Less connection finds its path and comes in action while DSN needs to configure the username and pass etc.
but it's true that DSN connections are more secure.

 

[PaulSc]

Thanks for your responses. Looks like DSNLess are easiest but fixed dsn's are 'safer'. Looks like fixed ones for us then.

Cheers

PaulSc.

 

[medic]

Guys,

How does a DSN-less connection becomes less secure if my database does not reside in any of the folders shared in the internet?

Medic