PC Review


Reply
Thread Tools Rate Thread

Code access permission to access processes running in memory

 
 
Simon Hart
Guest
Posts: n/a
 
      3rd Feb 2006
Does anyone know the standard code access permission to be able to
manipulate a process using the Process class?

Thanks
Simon.


 
Reply With Quote
 
 
 
 
Willy Denoyette [MVP]
Guest
Posts: n/a
 
      3rd Feb 2006

"Simon Hart" <srhartone@[no spam]yahoo.com> wrote in message
news:(E-Mail Removed)...
| Does anyone know the standard code access permission to be able to
| manipulate a process using the Process class?
|
| Thanks
| Simon.
|
|

Not sure what you mean with "code access permission", if you mean "security
privileges" then you'll need "SeDebugPrivilege".

Willy.


 
Reply With Quote
 
Simon Hart
Guest
Posts: n/a
 
      3rd Feb 2006
I want to request a permission using declarative permissions in my assembly
to grant permission to shut down processes. Namespace:
System.Security.CodeAccessPermission. I don't want to have to write my own.

Don't know what "SeDebugPrivilege" is?

"Willy Denoyette [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> "Simon Hart" <srhartone@[no spam]yahoo.com> wrote in message
> news:(E-Mail Removed)...
> | Does anyone know the standard code access permission to be able to
> | manipulate a process using the Process class?
> |
> | Thanks
> | Simon.
> |
> |
>
> Not sure what you mean with "code access permission", if you mean
> "security
> privileges" then you'll need "SeDebugPrivilege".
>
> Willy.
>
>



 
Reply With Quote
 
Willy Denoyette [MVP]
Guest
Posts: n/a
 
      3rd Feb 2006
There is no such standard permission attribute, so you will have to write
your own. Note that I'm not clear why you need this, I guess you could
restrict the applications who are able to stop other processes based on the
callers (the process or thread) identity.

"SeDebugPrivilege" is a windows security privilege, this one is required to
enable debuging and reading/writing into some other processes address space.
This is a user privilege and has nothing to do with CAS security.

Willy.



"Simon Hart" <srhartone@[no spam]yahoo.com> wrote in message
news:(E-Mail Removed)...
|I want to request a permission using declarative permissions in my assembly
| to grant permission to shut down processes. Namespace:
| System.Security.CodeAccessPermission. I don't want to have to write my
own.
|
| Don't know what "SeDebugPrivilege" is?
|
| "Willy Denoyette [MVP]" <(E-Mail Removed)> wrote in message
| news:(E-Mail Removed)...
| >
| > "Simon Hart" <srhartone@[no spam]yahoo.com> wrote in message
| > news:(E-Mail Removed)...
| > | Does anyone know the standard code access permission to be able to
| > | manipulate a process using the Process class?
| > |
| > | Thanks
| > | Simon.
| > |
| > |
| >
| > Not sure what you mean with "code access permission", if you mean
| > "security
| > privileges" then you'll need "SeDebugPrivilege".
| >
| > Willy.
| >
| >
|
|


 
Reply With Quote
 
Simon Hart
Guest
Posts: n/a
 
      3rd Feb 2006
I've written a C# Windows Service which runs on servers 2000, 2003 etc which
manages our surrogate processes and shuts them down if they are rogue.
The problem when running on a 2003 server by default the SYSTEM account
under 2003 server does not have permissions to shutdown processes and no
error exceptions are fired.
I might use the WindowsPrincipal class and use IsInRole to determine if the
process is running as an administrator instead of writing my own custom
permission class which is alot of hastle to develop then it would need to be
deployed.

"Willy Denoyette [MVP]" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> There is no such standard permission attribute, so you will have to write
> your own. Note that I'm not clear why you need this, I guess you could
> restrict the applications who are able to stop other processes based on
> the
> callers (the process or thread) identity.
>
> "SeDebugPrivilege" is a windows security privilege, this one is required
> to
> enable debuging and reading/writing into some other processes address
> space.
> This is a user privilege and has nothing to do with CAS security.
>
> Willy.
>
>
>
> "Simon Hart" <srhartone@[no spam]yahoo.com> wrote in message
> news:(E-Mail Removed)...
> |I want to request a permission using declarative permissions in my
> assembly
> | to grant permission to shut down processes. Namespace:
> | System.Security.CodeAccessPermission. I don't want to have to write my
> own.
> |
> | Don't know what "SeDebugPrivilege" is?
> |
> | "Willy Denoyette [MVP]" <(E-Mail Removed)> wrote in message
> | news:(E-Mail Removed)...
> | >
> | > "Simon Hart" <srhartone@[no spam]yahoo.com> wrote in message
> | > news:(E-Mail Removed)...
> | > | Does anyone know the standard code access permission to be able to
> | > | manipulate a process using the Process class?
> | > |
> | > | Thanks
> | > | Simon.
> | > |
> | > |
> | >
> | > Not sure what you mean with "code access permission", if you mean
> | > "security
> | > privileges" then you'll need "SeDebugPrivilege".
> | >
> | > Willy.
> | >
> | >
> |
> |
>
>



 
Reply With Quote
 
Willy Denoyette [MVP]
Guest
Posts: n/a
 
      3rd Feb 2006
Weird, SYSTEM should have this privilege, are you sure the service runs as
"localsystem", on W2K3 services run by default as 'local service" which has
no such privilege.

Willy.

"Simon Hart" <srhartone@[no spam]yahoo.com> wrote in message
news:(E-Mail Removed)...
| I've written a C# Windows Service which runs on servers 2000, 2003 etc
which
| manages our surrogate processes and shuts them down if they are rogue.
| The problem when running on a 2003 server by default the SYSTEM account
| under 2003 server does not have permissions to shutdown processes and no
| error exceptions are fired.
| I might use the WindowsPrincipal class and use IsInRole to determine if
the
| process is running as an administrator instead of writing my own custom
| permission class which is alot of hastle to develop then it would need to
be
| deployed.
|
| "Willy Denoyette [MVP]" <(E-Mail Removed)> wrote in message
| news:%(E-Mail Removed)...
| > There is no such standard permission attribute, so you will have to
write
| > your own. Note that I'm not clear why you need this, I guess you could
| > restrict the applications who are able to stop other processes based on
| > the
| > callers (the process or thread) identity.
| >
| > "SeDebugPrivilege" is a windows security privilege, this one is required
| > to
| > enable debuging and reading/writing into some other processes address
| > space.
| > This is a user privilege and has nothing to do with CAS security.
| >
| > Willy.
| >
| >
| >
| > "Simon Hart" <srhartone@[no spam]yahoo.com> wrote in message
| > news:(E-Mail Removed)...
| > |I want to request a permission using declarative permissions in my
| > assembly
| > | to grant permission to shut down processes. Namespace:
| > | System.Security.CodeAccessPermission. I don't want to have to write my
| > own.
| > |
| > | Don't know what "SeDebugPrivilege" is?
| > |
| > | "Willy Denoyette [MVP]" <(E-Mail Removed)> wrote in message
| > | news:(E-Mail Removed)...
| > | >
| > | > "Simon Hart" <srhartone@[no spam]yahoo.com> wrote in message
| > | > news:(E-Mail Removed)...
| > | > | Does anyone know the standard code access permission to be able to
| > | > | manipulate a process using the Process class?
| > | > |
| > | > | Thanks
| > | > | Simon.
| > | > |
| > | > |
| > | >
| > | > Not sure what you mean with "code access permission", if you mean
| > | > "security
| > | > privileges" then you'll need "SeDebugPrivilege".
| > | >
| > | > Willy.
| > | >
| > | >
| > |
| > |
| >
| >
|
|


 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
80+Running processes and 50%+ physical memory john Windows Vista General Discussion 6 1st Apr 2009 08:00 PM
Running MS Access From Excel VBA: Communication Between Processes? PeteCresswell Microsoft Excel Programming 2 29th May 2008 03:59 PM
Access 2003 stops running with out of memory, but memory is there! =?Utf-8?B?QmFybmV5?= Microsoft Access VBA Modules 4 6th Jan 2006 04:43 PM
Automation - running code in one Access DB from another Access DB Phred Bear Microsoft Access VBA Modules 7 26th Jan 2005 04:10 AM
Permission errors running ASPs on Access db on network =?Utf-8?B?Qm9iIFN0ZW56?= Microsoft Frontpage 3 6th Feb 2004 03:31 AM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 09:10 PM.