Re: Windows service
- From: "Mr. Arnold" <MR. Arnold@xxxxxxxxxx>
- Date: Fri, 26 Oct 2007 14:16:04 -0400
"Chris Mullins [MVP - C#]" <cmullins@xxxxxxxxx> wrote in message news:OESylA$FIHA.1316@xxxxxxxxxxxxxxxxxxxxxxx
"Mr. Arnold" <MR. Arnold@xxxxxxxxxx> wrote
"Bela Istok" <bela_i@xxxxxxxxxxx> wrote in message news:F0EA16A6-A2DF-4B80-B823-592BCA8BED4B@xxxxxxxxxxxxxxxxArnold If you store the logins in the App.Config you can compromise the server if someone get to the machine, the best way is to use integrated in the service (if the service is running in the user stations).
You do know that you can encrypt a configuration file in .NET 2.0 don't you?
http://www.codeproject.com/useritems/Configuration_File.asp
While that's an option, it's a real pain. Worse, it's still less secure that using Windows Auth to the SQL DB. I've actually done this before (we were hitting an Oracle DB that didn't support Windows Auth), using both the COM+ method recommend by the PAG group, and using the DPAPI method others have recommended. It worked, but it's alot of overhead both for the devs and the sys admins to worry about.
If you can use it, Windows Auth to the SQL Database is better in every way.
It's only good for a solution that's running in a domain. It's not good for a solution that the users are not in a NT domain environment. I have not seen NT Authenticated user used for a means of connecting to a SQL Server database by any application, even in a domain. That seems to be a PITA for a DBA, and I think they avoid it, at least the ones I have worked with. Some DBA's have a special sequence of characters to kind of encrypt the psw a kind of their own blend or take on the psw.
.
- Follow-Ups:
- Re: Windows service
- From: Chris Mullins [MVP - C#]
- Re: Windows service
- References:
- Windows service
- From: Rotsey
- Re: Windows service
- From: Rotsey
- Re: Windows service
- From: Mr. Arnold
- Re: Windows service
- From: Bela Istok
- Re: Windows service
- From: Mr. Arnold
- Re: Windows service
- From: Chris Mullins [MVP - C#]
- Windows service
- Prev by Date: Re: Generic import service for multiple Database providers.
- Next by Date: Re: Windows service
- Previous by thread: Re: Windows service
- Next by thread: Re: Windows service
- Index(es):
Relevant Pages
|