| .NET Security |
| C# Corner |
| I basically wanted to programmatically check whether the user had the relevant permissions by accessing their windows account. Fortunately, .NET provides this through the System.Security.Principal namespace. I also wanted to deny access to particular drives - this is done through the namespace System.Security.Permissions. |
|
| Code Access Permissions |
| MSDN |
| Code access permissions are permission objects that are used to protect resources and operations from unauthorized use. They are a fundamental part of the common language runtime's mechanism for enforcing security restrictions on managed code. |
|
| Custom Permissions |
| C#Today |
| Any multi user system needs to have a concept of security to protect one users data from another. This security element could be anything from granting or denying a user access to a file, a network share, or certain entities in a database. These security mechanisms are controlled via the use of Permissions. Before the advent of .NET, using permissions in application code was hard, but now the framework allows a very open and extensible permission architecture. In this article, the third of the week's security-based articles, Kaushal Sanghavi explores the support that the .NET framework offers for working with permissions, and demonstrate how developers can design their own custom permissions to control access to protected data. |
|
| High-Performance .NET Application Development & Architecture |
| DotNetJunkies |
| It has always been a goal of project architects to plan an effective strategy from the ground up in regards to an new application. All relevant factors are taken into consideration with respect to the application, from its design and layout to a functional website infrastructure. |
|
| Return of the Rich Client: Code Access Security and Distribution Features in .NET Enhance Client-Side Apps |
| MSDN |
| Rich clients employ many of the features and conveniences of the operating system they run on, and the list of these features has been growing since the dawn of the PC. But as apps have migrated to the Web, the trend towards increasing client-side functionality has ground to a virtual halt. There are several reasons for this; chief among them are security and deployment problems. But that's all about to change. With the .NET Framework, you can participate in building the distributable rich client of the future. In this article, the author enumerates the pertinent features of .NET that will allow you to build safe, easily deployable controls. The features discussed include managed code, code access security, versioning control, Windows Forms classes, and isolation.. |
|
| Security in .NET |
| C# Corner |
| .NET is Microsoft’s next strategic step for running distributed and service-oriented systems over the Internet. To reach this target Microsoft has introduced a new security model, called Code Access Security. Developers and administrators will have to differentiate between this model and the already well-known Role-Based security model. |
|
| Security in .NET: Enforce Code Access Rights with the Common Language Runtime |
| MSDN |
| Component-based software is vulnerable to attack. Large numbers of DLLs that are not tightly controlled are at the heart of the problem. Code access security in the Common Language Runtime of the Microsoft .NET Framework addresses this common security hole. In this model, the CLR acts as the traffic cop to assemblies, keeping track of where they came from and what security restraints should be placed on them. Another way the .NET Framework addresses security is by providing preexisting classes which have built-in security. |
|
| Understanding .NET Code Access Security |
| C# Corner |
| When we are running an application and we need to run a feature for which, the application does not have the relevant module, the application connects to the Internet and downloads the module into the Global Assembly Cache (GAC) and begins executing. This is done without being prompted to us. |
|