• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 356
  • Last Modified:

Process.GetProcesses() and User Privilege

I have a VS 2003 C# application that works fine in most environments.  It has recently been installed in a corporate environment (WinXP / Server 2003) where the user workstations are pretty well 'tightened-down' from a security point of view.  The application makes use of Process.GetProcesses() and it appears that the application throws an exception when this is called due to insufficient privilege.  So my question is -- from a security perspective, what changes in groups or policy (or whatever) need to be made such that Process.GetProcesses() will not throw?  Obviously, making everyone an admin would solve the problem, but I am looking for something a bit more targeted and minimalistic that will keep their administrator happy.

1 Solution
The System.Diagnostics.Process.GetProcesses method requires the calling assembly to be fully trusted by the .NET Framework.  You may consider signing your assembly and then deploying an enterprise policy that includes the required permissions.

  Signing an Assembly with a Strong Name

  .NET Framework Enterprise Security Policy Administration and Deployment
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Train for your Pen Testing Engineer Certification

Enroll today in this bundle of courses to gain experience in the logistics of pen testing, Linux fundamentals, vulnerability assessments, detecting live systems, and more! This series, valued at $3,000, is free for Premium members, Team Accounts, and Qualified Experts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now