CLR Security in .NET 3.5

06/13/2009

Support for “Suite B” crypto algorithms on Vista
Elliptic Curve Diffie Hellman for key exchange (ECDiffieHellmanCng class)
Elliptic Curve Digital Signature Algorithm for signing (ECDsaCng class)
FIPS certified Advanced Encryption Standard (AES) for symmetric encryption (AesCryptoServiceProvider class)
FIPS certified SHA2 for cryptographic hashing (SHA256Cng or SHA256CryptoServiceProvider classes)
Support for the trusted publisher list for managed controls in the browser
Enables a simple elevation model for controls in the browser
New opt-in reflection security model
Apps can reflect on the private members of libraries at the same or lower trust level
Useful for script engine scenarios

NOTES:

http://blogs.msdn.com/shawnfa/

System.Security.crypto

Suite B – Gov. stronger crypto. Modern algorithms. Vista API’s.

ECDSA - Data, code signing.

FIPS – secret key to encrypt data, FIPS – checksum.

Trusted Pub - Object tag in browser for managed control (if .Net is installed), Adding signed control and stick it in trusted list. Built into IE/Orcas. Add cert signed with, to the trusted publisher list on the client. Sign ctrl and deploy cert.

Opt-in: Trusted reflection previously required FT without this. Need to add new opt-in permission to permset. Script engine could be untrusted…

Posted in: .NET Framework| Tags: .NET 3.5 CLR Security Support class crypto list browser suite

System Requirements of Enterprise Library 4.1

06/12/2009

For all application blocks except for the Unity Application Block, the Enterprise Library core features, and the configuration tools, the minimum requirements are:

Microsoft Windows XP Professional, Windows Server 2003, Windows Server 2008, or Windows Vista operating system
Microsoft .NET Framework 3.5 or later
Microsoft Visual Studio 2008 development system (any of the following editions):
Standard Edition
Professional Edition
Team Edition for Software Developers
Team Edition for Software Testers
Team Edition for Software Architects
Team Suite

Note:
The Unity Application Block is a general-purpose dependency injection mechanism designed for use in applications that run on the .NET Framework 2.0 and later. It is not limited to use only within Enterprise Library. For details of the system requirements and development software requirements for the Unity Application Block, see System Requirements for the Unity Application Block.

To run the Unit Tests, the following is also required:

Visual Studio 2008 Professional or Visual Studio 2008 Team Edition. Enterprise Library includes both unit test binaries and source code. You need a version of Visual Studio that supports unit tests. For instructions about how to use the unit tests, see Unit Tests. If you modify the unit test source, you will need to recompile it, which also requires Visual Studio 2008 Professional or Visual Studio 2008 Team Edition.
For the Data Access Application Block, the following is also required:

A database server running a database that is supported by a .NET Framework 3.5 data provider. This includes SQL Server 2000 or later, SQL Server 2005 Compact Edition, and Oracle 9i or later. The database server can also run a database that is supported by the .NET Framework 3.5 data providers for OLE DB or ODBC.
For the Logging Application Block, the following is also required:

Stores to maintain log messages. If you are using the MsmqTraceListener trace listener to store log messages, you need a message queue. If you are using the DatabaseTraceListener trace listener to store log messages, you need a database server. If you are using the EmailTraceListener trace listener to store log messages, you need an SMTP server.

Posted in: .NET Framework| Tags: Enterprise Library Requirements .NET 3.5 Block team database enterprise server visual unit system edition studio

Hot Posts

Latest posts

Tags

Others

Sponsors