Re: Appl. Security Problems

From: Nicole Calinoiu (calinoiu)
Date: 05/24/05 

Date: Tue, 24 May 2005 06:51:55 -0400

"Steve B." <SteveB@discussions.microsoft.com> wrote in message
news:A40F8CFA-F5E0-45B1-AC61-98B31FFECA70@microsoft.com...
> Nicole
>
> Are there instructions on how trust a directorory and the files within it.

You would simply need to use a URL membership condition rather than a strong
name membership condition when you create the new code group. However,
getting the URL right can be a bit tricky since it must match the URL used
by the CLR to load the assemblies.

> I have separate strong names for each project within the file VS solution.
> Should I have one strong name for the whole solution?

By definition, each assembly would have a distinct strong name, so I suspect
you're actually concerned about different signing keys. It is rather
unusual to use a different signing key for each project within a solution.
The "typical" schemes are to use a single signing key for all assemblies
released by an organization, or for all assemblies released in a given
product group. Since all projects within your solution presumably form part
of the same product, they would usually be signed with the same key under
either scheme.

>
>
>
> "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: Locking down CAS policy
    ... they use the $AppDirUrl$ and $CodeGen$ url membership condition - if you want to base everything on strong name - you have to strong name all your pages, code behinds and App_Code files....this can be accomplished by modifying the element to specify a keyfile... ... you shouldn't mock with the existing code groups - they grant the ... "ASP.Net" permission set to code running in you app dir and the temp ... I've used the Evaluate Assembly utility to check the assemblies in ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • RE: Custom Membership Condition
    ... >Subject: RE: Custom Membership Condition ... >implementing IMembershipCondition, ... >add it to the Security Policy Assemblies list. ...
    (microsoft.public.dotnet.security)
  • Re: IL-to-IL "front-end-compiler" ... ?
    ... Working with IL OpCodes is ... assemblies would be extremely difficult to develop properly. ... NOP and other instructions are emitted when I thought ... I have since realized I did not properly cast the values ...
    (microsoft.public.dotnet.framework)
  • Re: Failed to Load WSE 2.0 Add-in into VS.NET (CAS-problem)
    ... maintain full trust to their own assemblies. ... >> Assembly evidence must match this membership condition to belong to the ... > exact path that will be used at runtime, and finding that exact path can ... >> receive Fullthrust, so VS.NET is therefore not partially thrusted. ...
    (microsoft.public.dotnet.security)
  • Re: NUnit and StrongnameIdentityPermission
    ... If you are using link demands instead of full stack demands, ... be an issue if you sign your test assembly with the same signing key. ... Re-compile NUnit from its source (available in the NUnit install ... > our company's key on the public interfaces of some of the assemblies. ...
    (microsoft.public.dotnet.security)