Re: .Net & Administrator Previlages

From: Alek Davis (alek.davisATintel.com)
Date: 02/18/03 

From: "Alek Davis" <alek.davisATintel.com>
Date: Tue, 18 Feb 2003 09:36:05 -0800

I think that a developer does not necessarily need to be a local
administrator. Being a member of the Power User, Debugger Users, and/or VS
Developers groups should probably be enough. I may be wrong here, though.

I would tend to agree with the other guys: being a developer without
administrative rights on your own development machine may be a daunting
experience, because often you need to perform tasks such as changing
registry settings, creating local groups and users, modifying system
policies, installing additional software, running system tools, etc. And I
would never understand what the reasons of concern would be. It is normally
either a support issue (e.g. in our organization PC users are not supposed
to be local admins just to make it easier for tech support to troubleshoot
problems when they arise, but the problem is that developers normally know
more about PCs than tech support, so it becomes a moot point, so most of
developers prefer to have unsupported systems and fix issues themselves
rather than being crippled by the bad policy) or it is a security issue,
which is not really an issue at all because the user has rights on his PC
only, so I do not see what security problem this would likely to cause.

It is important to distinguish that developers should normally not write
software requiring administrative privileges to run, but this is a different
story.

-- Alek

"payman" <paymanzafar@yahoo.com> wrote in message
news:038401c2d4c7$39d20200$a401280a@phx.gbl...
> Alek
>
> I want to ask
> Is it possible that we do not give the "local
> administrator privilages" to software developers?
>
> In other words what privilages should be assigned to these
> users to be able to do software development tasks
> under .Net?
>
> Thanks.
>
> >-----Original Message-----
> >Payman,
> >
> >I am afraid that you are not going to get your question
> answered, because it
> >is not clear what you are asking. Could you clarify what
> you meant by
> >"preserve security" and "along with .Net application
> development"?
> >
> >-- Alek
> >
> >"payman" <paymanzafar@yahoo.com> wrote in message
> >news:01ca01c2d037$bfb62840$a001280a@phx.gbl...
> >> Our company is developing internet applications
> under .Net
> >> framework. But it requires that the user to be a member
> of
> >> local administrators group.
> >>
> >> Is there a method to preserve security along with .Net
> >> application development?
> >>
> >> Thanks for your help.
> >>
> >
> >
> >.
> >

Relevant Pages

  • Re: Permissions issue
    ... Don't change permissions in situations you are not sure why you are doing it. ... There was in the past a MSDN forum for developers of applications in Vista but I am not sure where it is now. ... The following has multiple forums that might be relevant and that would already have previous answers. ... How can I provide access to this program to administrator users, ...
    (microsoft.public.windows.vista.security)
  • Re: SQL Server Security Best Practices
    ... So my assumption is there is not documentation specifying Developers, ... don't want Developers to have certain access, DBA's, System Admins. ... Developers why they don't need Local Administrator, ...
    (microsoft.public.sqlserver.security)
  • Re: .Net & Administrator Previlages
    ... I tend to agree with Adam that developers often need Administrative ... privileges to do a lot of the things they need to do ... are also some really good reasons to not run as Administrator by default. ... >> administrator privilages" to software developers? ...
    (microsoft.public.dotnet.security)
  • Re: does a developper need admin access to SPS...
    ... I would suggest that the developers should use Virtual Servers, ... > grey area which does not allow this split-up, ... > needs to be local administrator on the server. ...
    (microsoft.public.sharepoint.portalserver.development)
  • Re: Group Policy
    ... > administrator password is a tad difficult as it ties into ... > We tried to disable local logon in the default domain ... Well i'd personally have the errant developers, whoever gave them the admin ...
    (microsoft.public.windows.server.general)