Securing a control assembly against use of foreign assemblies

From: Jürgen Bayer (jb42[nospam)
Date: 08/03/05 

Date: Wed, 3 Aug 2005 14:14:28 +0200

Hi all,

I know how to use the StrongNameIdentityPermission attribute to secure an
assembly against callers which have no strong name with the given public
key. Securing controls is problematic, since the Visual Studio (7) designer
has no strong name (even if it would, the public key would be another). So
dragging a secured control from the tooolbar results in a SecurityException.
The only workaround I know is, to only secure the public methods of the
control (except InitializeComponent). But this does not satisfy the security
guidlines of the company I work for.

Does anyone know another workaround to secure controls in a way that allows
the using in the VS designers?

Is this problem fixed in 2.0?

Thanks in advance

Juergen Bayer

Relevant Pages

  • RE: application security
    ... Securing Authentication into the applications ... Securing Access control to resources in the application ... Netegrity plays a role in Authentication and Access control ... If you are trying to build the most secure application, ...
    (Security-Basics)
  • Re: Which Windows OS is Safest
    ... It's not specifically which is the safest OS, but how you go about securing ... These will help make any OS secure. ... >> I would like to know what is regarded as the safest Windows OS as I ...
    (Security-Basics)
  • Re: LOGIN INFO secure at wwww.americanexpress.CA?
    ... a session, and all was secure. ... the particular point of concern was securing the login info itself, ... My guess is that the quality of support at Amex is such that they never ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: Looking for One Time Pad Software, small with gui for WIN.
    ... Yes - securing the computer is the key to preventing a side-channel ... attack it. ... So if your OTP is implemented using secure, ... But the OP was talking about a OTP on a Windows PC. ...
    (sci.crypt)
  • Re: Does FE mde need security?
    ... you are learning from your mistakes so this is just part of your learning process. ... In some situations just properly securing the BE will do just fine. ... If you secure the BE and the FE using the same workgroup file then no, ... you will not see two login screens. ...
    (microsoft.public.access.security)