Re: StrongNameIdentityPermission problem

"ed" <ed@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CCAB5A56-E600-4439-9468-36B096DE5CF5@xxxxxxxxxxxxxxxx
"Nicole Calinoiu" wrote:

This is not expected behaviour under version 1.1 of the .NET Framework.
Are
you calling SensitiveRoutine directly from C.exe, or is the call being
made
by invoking a method in A.dll or B.dll that then invokes SensitiveRoutine?

[ED]
Yes, I called the sensitive routine directly from the .exe(s)

Are you absolutely certain that C.exe is signed with a different key? If
so, could you please post the exact code used for your SNIP attribute?


[ED]
I need that my routine ONLY be called from a strong named assembly signed
with my key, no one other can do it.

It simply isn't possible to completely prevent calls into your method by
undesired callers. Highly privileged code run by a highly privileged
attacker will always be able to bypass whatever protection you add. Might
you be able to share a bit more detail about how your application is
deployed and who you are attempting to protect against?


.