Securing the connection string (mainly the password within the string)

From: Neil Kiser (neil_at_NO_SPAM_PLEASEkiserville.com)
Date: 10/01/04 

Date: Thu, 30 Sep 2004 20:05:55 -0500

I may be off-base here, but I seem to recall some discussion about the
fact that .Net code isn't particularly secure. I believe that this is
what the 'obfuscator' discussions are all about. (again, feel free to
correct me if I've got it wrong).

So this got me thinking about the fact that I need a safe place to
store the database password. I wasn't planning on giving the password
to the user. I was going to encrypt the database and setup a password
(this in on SQL Server CE 2.0) and the app would hold the password.

Am I safe preparing an assembly that contains the password? Is it a
pipedream to believe that the password will not be uncovered?

Thanks,
-Neil K.

Relevant Pages

  • Re: Securing the connection string (mainly the password within the string)
    ... exists that will secure your passwork from being discovered. ... or by encryption. ... > store the database password. ... > Am I safe preparing an assembly that contains the password? ...
    (microsoft.public.sqlserver.ce)
  • Re: Secure BE
    ... I'm having traouble figuring out how to secure the ... > accessed via a shortcut which references the server based workgroup. ... > of the clients can just open up the BE if they figure out the location and ... If you set a database password on the BE you then need to delete the linked ...
    (microsoft.public.access.security)
  • Re: Database password
    ... Robert wrote: ... database password, how secure is it? ... About as weakly as you can imagine except for Access 2007 where I hear it has ...
    (microsoft.public.access.security)
  • Re: Set single dbase password
    ... The database password is easier to crack, ... Joan Wild ... > If we wanted to secure a database simply to stop 3rd parties from ... > disadvantages with simply using the Set Database Password option ...
    (microsoft.public.access.security)