assert permissions

From: Lilleman (Lilleman@mbox309.swipnet.se)
Date: 01/28/03 

From: "Lilleman" <Lilleman@mbox309.swipnet.se>
Date: Tue, 28 Jan 2003 13:11:51 +0100

The dotNet framework has some abilities to assert permissions. I understand
the technical use of assertion, but why has Microsoft chosen to solve the
problem this way? With asserting as
an option, the whole code security model is jeopardized. It feels like
the assert option is a risky compromise between a security architecture
and user friendliness and options to developers.

Is it possible to encrypt the information that is sent between manage and
unmanaged code?

Quantcast