Re: When a service really starts
From: Bruce Parker (bparkerhsd_at_nospam.nospam)
Date: 03/05/05
- Next message: SB: "Re: Hex function"
- Previous message: gaidar: "Re: Import into Word"
- In reply to: Sean Hederman: "Re: When a service really starts"
- Next in thread: Sean Hederman: "Re: When a service really starts"
- Reply: Sean Hederman: "Re: When a service really starts"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 5 Mar 2005 10:21:02 -0800
Does this mean if I put the code in the constructor to change the logon
credentials it is too late?
In addition, this is not a security hole. A network administrator provides
this information via another secured application which is required by our
software. The service obtains this information from the secured application.
Without going into details, it becomes a security risk if the logon
credentials does not match the one the network administrator provides in the
other application.
I need a definitive answer on this question.
"Sean Hederman" wrote:
> "Bruce Parker" <bparkerhsd@nospam.nospam> wrote in message
> news:F531A640-B232-45C7-95F3-E7876A1DD714@microsoft.com...
> >I have written a .NET Service. In the OnStart method, I am setting the
> > Services user name and password. Has the service already obtained this
> > information at this point and is using the existing information? Is this
> > the
> > right place to do this in the service's code?
>
> Yes, the Service Controller starts your process up with the credentials
> indicated. You don't have to change anything as far as that is concerned. In
> fact I would consider it a pretty serious security hole to have a service
> change it's own logon credentials.
>
>
>
- Next message: SB: "Re: Hex function"
- Previous message: gaidar: "Re: Import into Word"
- In reply to: Sean Hederman: "Re: When a service really starts"
- Next in thread: Sean Hederman: "Re: When a service really starts"
- Reply: Sean Hederman: "Re: When a service really starts"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|