X-Git-Url: http://wien.tomnetworks.com/gitweb/?a=blobdiff_plain;f=web%2Fcrypto;h=56fbde78316e3f083ccb3948acc992ef7ce563bb;hb=48c29f2fa4a3198164c7c9dae4b1eb2f9f31315a;hp=90fadc5fd6d4fc8c6bd37060cbe040df8b01a44e;hpb=527e26adfab78735b4a42e9796de499211325cfb;p=mono.git diff --git a/web/crypto b/web/crypto index 90fadc5fd6d..56fbde78316 100644 --- a/web/crypto +++ b/web/crypto @@ -1,7 +1,8 @@ * Cryptography In the .NET framework cryptography can be found under a number of - namespaces in several assemblies. + namespaces in several assemblies. Mono also has it's own assemblies + to provide missing security functionalities from the .NET framework. ** Assembly: corlib @@ -11,61 +12,14 @@ **** Status -**** TODO - - -**** Notes - - - *** Namespace: System.Security.Cryptography.X509Certificates **** Status @@ -74,49 +28,21 @@ (using the Mono.Security.ASN1 class). * Software Publisher Certificates (SPC) used by Authenticode - (tm) to sign assemblies are supported (extraction from PE - files) but not yet validated. + (tm) to sign assemblies are supported and minimally + validated. * Unit tests are generated from a set of existing certificates (about a dozen) each having different properties. Another - set of certificates (more than 300) are used for a more + set of certificates (more than 700) are used for a more complete test (but isn't part of the standard test suite for - size and time consideration, i.e. a 3.5Mb C# source file). - - -**** TODO - **** Notes
@@ -130,29 +56,25 @@ **** Status - -**** TODO -
** Assembly: Mono.Security - Rational + Rational: This assembly provides the missing pieces to .NET security. On Windows CryptoAPI is often used to provide much needed functionalities (like - some cryptographic algorithms, code signing, X.509 certificates). + some cryptographic algorithms, code signing, X.509 certificates). Mono, + for platform independance, implements these functionalities in 100% + managed code. *** Namespace: Mono.Security +*** Notes + +
** Tools There are many tools in the .NET framework that indirectly interacts - with some cryptographic classes. Mono will eventually need these tools. - Unless noted the tools should work on any CLR (tested with both Mono - and Microsoft). + with some cryptographic classes. Unless noted the tools should work on + any CLR (tested with both Mono and Microsoft). **** Status - The following tools are complete: + The following tools are complete (or mostly complete): -**** TODO - The following tools are still missing or incomplete: + Somewhat usable, somewhat incomplete: - * signcode and chktrust (in progress) - for signing and validating Authenticode(tm) signatures on - assemblies (or any PE file). +**** TODO + The following tools are still missing or largely incomplete: + @@ -326,33 +296,40 @@ tools are of limited use until supported by the runtime.
-** Other stuff +** References - - -
-** How to Help - - Complete any of the TODO (and feel good about it ;-). + * RSA Laboratories' + Frequently Asked Questions About Today's Cryptography, Version 4.1 - Add missing unit tests to classes or methods. + * Public-Key Cryptography Standards ( + PKCS) - Write some documentation on the cryptographic classes for the - Mono - Handbook as I'm not a very good writer (at least in English). + * National Institute of Standards and Technology - Federal + Information Processing Standards + NIST FIPS + - Optimization can also be done on algorithms as crypto is never fast - enough. Just be sure to test every optimization (using the unit test) - carefully - it's so fast to break an algorithm ;-). +
+** How to Help - Contact Sebastien Pouliot (home - , work) if you need additional - informations about the status of the cryptographic classes. +
-Last reviewed: April 7, 2003 (post mono 0.23) +Last reviewed: June 26, 2004 (mono release candidate 1)