Use public/private keys to verify sending assembly

[qdm]

Hello any crypto and remoting types ... can you lend an ear? I would
like to enhance the security of an existing application. Currently,
the client tier of the application makes remoting calls to the
business tier. At the business tier, I want to verify that remoting
call originated from an assembly that was signed using my company's
private key. The middle tier will assembly will signed in the same
way. Has anyone experience, or just a good idea for doing this? In
the client, I do have the freedom to send what I want in the call
context.

Any help or thoughts are deeply appreciated!

 

[Dave]

I'd ask this in the microsoft.public.dotnet.security group.