Re: Meaning/consequences of Unrestricted=true
From: Ivan Medvedev [MS] (ivanmed_at_online.microsoft.com)
Date: 08/27/03
- Next message: Keith Patrick: "Re: Meaning/consequences of Unrestricted=true"
- Previous message: Joe Kaplan \(MVP - ADSI\): "Re: ASPNET Event Log Access"
- In reply to: Keith Patrick: "Re: Meaning/consequences of Unrestricted=true"
- Next in thread: Keith Patrick: "Re: Meaning/consequences of Unrestricted=true"
- Reply: Keith Patrick: "Re: Meaning/consequences of Unrestricted=true"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 27 Aug 2003 11:18:52 -0700
Unrestricted=true is basically a statement saying that the whatever can be
expressed with the permission is flagged. For example if in some future
version of the permission there is going to be something else in addition to
Open/Save, the unrestricted permission state compiled with the old version
will automatially mean Open/Save/<new_thing> when run on a new version.
Hope my explanation is not too confusing :-)
--Ivan
This message is provided "AS IS" with no warranties, and confers no rights.
"Keith Patrick" <richard_keith_patrick@hotmail.com> wrote in message
news:%23xASLzKbDHA.2344@TK2MSFTNGP09.phx.gbl...
> OK, after digging a bit, I found that for some strange (at least to me)
> reason, ServiceProcess references System.Windows.Forms (why a service
> inherently has a link to UI stuff is beyond me; services really should not
> interact with the desktop directly). For that reason, I suspect that the
> unrestricted thing blows up. If instead I say "Open=false, Save=false",
it
> runs fine. Of course, this leads to another issue: if Open/Save are the
> only properties you can set on that permission, how does it differ from
> saying Unrestricted=true?
>
>
>
> "Ivan Medvedev [MS]" <ivanmed@online.microsoft.com> wrote in message
> news:OwcEIG%23aDHA.2668@TK2MSFTNGP09.phx.gbl...
> > Keith -
> > what is the exception's stack trace and message?
> > Unrestricted=false means basically that you are not refusing anything.
> > --Ivan
> > This message is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "Keith Patrick" <richard_keith_patrick@nospamhotmail.com> wrote in
message
> > news:%23gcdMq3aDHA.132@tk2msftngp13.phx.gbl...
> > > 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?
> > >
> > >
> >
> >
>
>
- Next message: Keith Patrick: "Re: Meaning/consequences of Unrestricted=true"
- Previous message: Joe Kaplan \(MVP - ADSI\): "Re: ASPNET Event Log Access"
- In reply to: Keith Patrick: "Re: Meaning/consequences of Unrestricted=true"
- Next in thread: Keith Patrick: "Re: Meaning/consequences of Unrestricted=true"
- Reply: Keith Patrick: "Re: Meaning/consequences of Unrestricted=true"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|