Re: Appl. Security Problems

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

Date: Tue, 24 May 2005 11:56:07 -0700

Nicole,

Sorry to to keep asking these questions, however, this is the most success
I've had in solving this problem so far.

After following the earlier post instructions the program opened up fine on
my machine but when I went to another user's machine I recieved the following
message:

Imported failed. The assmbly does not appear to be vailid ... strong name

What wrong?

The following is a typical configuration I have in each Visual Studio
project (file name(s): AssemblyInfo.cs) within the solution:

[assembly: AssemblyDelaySign(false)]
[assembly:
AssemblyKeyFile(@"C:\BusinessInformationSoftware\ADONetLibrary\obj\adoNetLibrary.snk")]
[assembly: AssemblyKeyName("")]

Steve

"Nicole Calinoiu" wrote:

>
> "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.
> >>
> >>
> >>
>
>
>