Re: Appl. Security Problems

From: Steve B. (SteveB_at_discussions.microsoft.com)
Date: 05/23/05


Date: Mon, 23 May 2005 11:32:22 -0700

Nicole

Are there instructions on how trust a directorory and the files within it.
I have separate strong names for each project within the file VS solution.
Should I have one strong name for the whole solution?

"Nicole Calinoiu" wrote:

> "Steve B." <SteveB@discussions.microsoft.com> wrote in message
> news:C86F5BC6-CB25-4DE9-965E-7FE50E8D986A@microsoft.com...
> > Local C# network application developed using VS .Net
> >
> > 1. While do some local network users able to Trust The Assembly via the
> > Control Panel .Net Framework wizard while others can not because of
> > "security
> > policy". Why?
>
> Probably because some of them are administrators and are adjusting the
> assembly permissions at the machine level, whereas others are non-admins and
> are only allowed to attempt to adjust the permissions at the user level.
> The "trust an assembly" wizard will usually give the "due to your existing
> security policy..." result you mentioned when run at the user level. (I'm
> unaware of any conditions under which a user-level run of the wizard would
> succeed.)
>
> BTW, it is possible for non-admins to restrict assembly permissions via
> other tools that modify the user-level CAS policy. However, under normal
> circumstances, low-privilege users cannot grant increase assembly
> permissions beyond those granted at the enterprise and machine levels.
>
>
> > 2. Why do I receive the following error message when I try to open my
> > ADONet dll from the network within my local .Net application?
> >
> > "The application attempted to perform an operation not allowed by the
> > security policy. The operation required the Security Exception. To grant
> > theis application the required permission please contact your system
> > administrator.."
> >
> > What do I or, my IT person, need to do to change security policy?
>
> See http://blogs.msdn.com/shawnfa/archive/2003/06/20/57023.aspx for
> instructions on how to modify the CAS policy for this scenario. See
> http://msdn.microsoft.com/library/en-us/cpguide/html/cpcondeployingsecuritypolicy.asp
> for some deployment options.
>
>
>



Relevant Pages

  • Re: Appl. Security Problems
    ... "Nicole Calinoiu" wrote: ... > are only allowed to attempt to adjust the permissions at the user level. ... >> What do I or, my IT person, need to do to change security policy? ... > instructions on how to modify the CAS policy for this scenario. ...
    (microsoft.public.dotnet.security)
  • Re: Publishing Software...
    ... I may have to recant my thoughts about it being a permissions issue, ... domain workstation security policy and then lock it down and reapply that. ... >> Are the users on the machines in question, members of the local Administrators group?? ... >> User Rights configuration was completed with one or more errors. ...
    (microsoft.public.windows.server.sbs)
  • Re: security permissions for creating a file
    ... it sounds like you might have modified your CAS policy. ... If you are running with modified policy, was it a deliberate change or not? ... configuration. ... If your assembly is granted unrestricted permissions under policy, ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: HTML embbeded (via <object> tag) Strong FullTrust Assemblies f
    ... Nicole, thank you for all of your precise help. ... >> Can an assembly with internet permissions running as an embedded object, ... > You seem to be mixing up the .NET Framework security policy and the IE ... You will most likely need to alter the client machine's .NET ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: security managment and policy monitoring
    ... >enable me to verify that an organization's security policy is being ... and in NT this would be the files that comprise the SAM database ... Once you have _all_ the data about files and permissions gathered, ... Then there's no single place where the relevant files might reside, ...
    (comp.security.misc)