Meaning/consequences of Unrestricted=true
From: Keith Patrick (richard_keith_patrick_at_nospamhotmail.com)
Date: 08/26/03
- Previous message: Ivan Medvedev [MS]: "Re: Obfuscators"
- Next in thread: Ivan Medvedev [MS]: "Re: Meaning/consequences of Unrestricted=true"
- Reply: Ivan Medvedev [MS]: "Re: Meaning/consequences of Unrestricted=true"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 25 Aug 2003 21:34:19 -0500
I've asked this before, but I still can't figure out what is going on.
Basically, I have a Windows Service that I'm trying to lock down. Just as
an experiment, I tried to apply the following attributes:
[assembly:AllowPartiallyTrustedCallers()]
[assembly:FileDialogPermissionAttribute(SecurityAction.RequestRefuse,
Unrestricted = true)]
While that has no adverse affects on a console app, I get a
SecurityException in my service. When I set Unrestricted to false, it works
fine, but I can't fathom why. My service definitely does not use file
dialogs, so the thing shouldn't have a problem. Could someone explain to me
why services don't like unrestricted permissions (every one I've tried has
this problem)? Also, if I set it to false for this permission, what exactly
does that mean?
- Previous message: Ivan Medvedev [MS]: "Re: Obfuscators"
- Next in thread: Ivan Medvedev [MS]: "Re: Meaning/consequences of Unrestricted=true"
- Reply: Ivan Medvedev [MS]: "Re: Meaning/consequences of Unrestricted=true"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]