Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
pelegk2
Aged Yak Warrior
723 Posts |
 Posted - 2005-10-10 : 06:53:11
|
| i was asked to "encode command tools for trusted connection"1)how can this be done?2)can i in some way make the command tools not accessible to any one ?Israel -the best place to live in aftr heaven 9but no one wan't to go there so fast -:) |
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2005-10-10 : 18:15:37
|
| What command tools? Do you mean Query Analyzer and Enterprise Manager? Don't install them on the client machines. But really, you're approaching security from the wrong side. You don't work to block a client tool, you lock down your security model on the server so that if a user somehow gets a client tool you didn't block, they still can't do any damage.What does it mean to "encode" them for "trusted connection"? If you don't want to use mixed authentication (which allows SQL Server Logins) that is a server setting. If you want to retain SQL Server Logins as an option but don't want you users using them, then don't give them the passwords.If what you really mean by "command tools" are applications that were written in-house, then you're just talking about changing the Connection String to use something like Integrated Security=SSPI instead of providing a User ID and Password in the connection string.---------------------------EmeraldCityDomains.com |
 |
|
|
|
|
|
encoding command tools for trusted connection