The One Who Was
Regular
Greetings:
I'm building a remote application that will verify with our server prior to running. The database it's verifying against is a SQL server. So I've opened the port required to establish the connection.
Now, my concern is, how easy would it be for someone to retrieve my connection string? Is the string encrypted at all? Can my .net application be reverse engineered and have my connection string compromised? Is there any way to beef up the security on this if it is a concern?
Also, what kind of security measures should I take on the server side? I've assigned the SA account a strong password, and Ive installed all the latest service packs I could find. I've even had our firewall accept SQL connections on a different port. Just curious if there is anything else I could look into.
This application is not a mission critical project, but just the same, I do not want anyone to have access to my connection string.
I'm building a remote application that will verify with our server prior to running. The database it's verifying against is a SQL server. So I've opened the port required to establish the connection.
Now, my concern is, how easy would it be for someone to retrieve my connection string? Is the string encrypted at all? Can my .net application be reverse engineered and have my connection string compromised? Is there any way to beef up the security on this if it is a concern?
Also, what kind of security measures should I take on the server side? I've assigned the SA account a strong password, and Ive installed all the latest service packs I could find. I've even had our firewall accept SQL connections on a different port. Just curious if there is anything else I could look into.
This application is not a mission critical project, but just the same, I do not want anyone to have access to my connection string.