Home/ Questions/Q 908715
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T16:45:38+00:00

I recently made a small app for a friend and then made it a

  • 0

I recently made a small app for a friend and then made it a public app, in doing so I forgot that it connects to my MS SQL DB and checks for values. Someone used Red Gate .Net Reflector to get my password and destroy it all. I’ve contacted their ISP and they are looking into it, apparently this person has a static ip with them.

So this is a lesson learned at a heavy price for me. How can I prevent this from happening again? How can I get away from the unsafe connection string they were able to use?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Never hard code connection strings. Use the configuration section provided for it (connectionStrings), and if really paranoid, encrypt it.

    If you are using a shared database, you should not even have a connection string on the client, but create a service point (for example a webservice) that will connect to the database on their behalf. The client can connect to this and your connection string is safe behind your service, which is in your control and on your server.

    • 0