**** TODO
<ul>
- * The current implementation of <code>CryptoStream</code> is
- very limited and contain known bugs (<a
- href="http://bugzilla.ximian.com/show_bug.cgi?id=40689">
- 40689</a>). The class need to be re-designed.
-
* RNGCryptoServiceProvider is currently only working on Linux.
The current implementation reside in Mono's runtime and use
the <code>/dev/[u]random</code> device (which do not exists
(using the Mono.Security.ASN1 class).
* Software Publisher Certificates (SPC) used by Authenticode
- (tm) to sign assemblies are supported (extraction from PE
- files) but <b>not yet</b> validated.
+ (tm) to sign assemblies are supported and <b>minimally</b>
+ validated.
* Unit tests are generated from a set of existing certificates
(about a dozen) each having different properties. Another
size and time consideration, i.e. a 7.5Mb C# source file).
</ul>
-**** TODO
- <ul>
- * Authenticode(tm) support is incomplete. We can extract the
- certificates from PE files but cannot validate the signature
- nor the certificate chain (and we're still missing some trust
- anchors). See Tools section for more information.
- </ul>
-
**** Notes
<ul>
* Except for their structure <b>there are no validation of the
continue to evolve to support the security tools.
* Microsoft implementation of <code>X509Certificate</code> is
- done by using CryptoAPI (unmanaged code). From the exceptions
- thrown Authenticode(tm) support is done via COM.
+ done by using CryptoAPI (unmanaged code). Based on the
+ exceptions thrown, Authenticode(tm) support is done via COM.
</ul>
<hr>
**** Status
<ul>
- * All classes are present but some (most Transforms) are only
- stubbed.
+ * All classes are present but some Transforms are only stubbed.
+
+ * We now have a fully managed C14N implementation.
* Most classes have their unit tests.
</ul>
**** TODO
<ul>
- * All the transforms needs to be done. But this requires far
- more XML knowledge than crypto. Note: Most tests runs because
- the feeded XML is pre-c14n (by hand in the code) before
- signing (not because the transforms works). In the short
- term <code>libxml2</code> could be used to provide C14N, but
- in the long term a fully managed class would be much better.
+ * Complete all Transform derived classes.
</ul>
<hr>
* Additional algorithms: MD2, ARCFOUR (required for SSL)
* Convertion helpers
</ul>
+*** Namespace: Mono.Security.Protocol.Tls
+ <ul>
+ * An 100% managed TLS implementation from Carlos Guzman Alvarez.
+ </ul>
*** Namespace: Mono.Security.X509
<ul>
* X.509 structures (certificate, CRL...) building and decoding.
**** Status
<ul>
- * Some part of the work has not yet been commited (still cleaning up).
-
* A big part of this assembly is also included inside Mono's
corlib. The classes are duplicated in this assembly so the
functionalities can be used without a dependency on Mono's
algorithms shouldn't be used in new design (MD4 is broken,
MD2 and MD5 aren't considered safe for some usage). They are
included to preserve interoperability with older applications
- (e.g. some old, but still valid, X.509 certificates use MD2).
+ (e.g. some old, but still valid, X.509 certificates use MD2,
+ MD4 is required for NTLM authentication ...).
</ul>
**** TODO
<a href="http://www.oasis-open.org/committees/wss/">OASIS</a> or
other committees.
- <b>[*] There are some licensing issues to consider before starting to
- implement WS-Security. All contributors must sign an agreement with
- Microsoft before commiting anything related to WS-Security into CVS.
- </b>
+*** Namespace: Microsoft.Web.Services.Security
+
+**** Status
+ <ul>
+ * Most WSE 1.0 classes are implemented.
+ </ul>
-*** Namespace: Microsoft.Web.Services.Security [*]
-*** Namespace: Microsoft.Web.Services.Timestamp [*]
+**** TODO
+ <ul>
+ * Some classes from System.Security assembly need to be
+ duplicated (and somewhat fixed) in WSE for XMLDSIG.
+
+ * There are still missing classes and <b>many</b> missing
+ unit tests.
+ </ul>
+
+
+*** Namespace: Microsoft.Web.Services.Timestamp
**** Status
<ul>
- * Nothing (yet) commited in CVS <b>[*]</b>.
+ * This seems complete for WSE 1.0 but some new classes were
+ introduced in WSE 2.0.
</ul>
*** Namespace: Microsoft.Web.Services.Security.X509
**** Status
<ul>
- * Nothing (yet) commited in CVS. However the classes in this
- namespace are outside WS-Security scope. So development, for
- those classes, could be done without signing any agreements.
+ * X509Certificate support is complete for both WSE 1.0 and 2.0.
</ul>
**** TODO
keypairs. This could also be used to store the SPC roots.
</ul>
+*** Notes
+ <ul>
+ * Microsoft has <a href="http://microsoft.com/downloads/details.aspx?FamilyId=21FB9B9A-C5F6-4C95-87B7-FC7AB49B3EDD&displaylang=en">released</a>
+ a technical preview of WSE 2. <b>Note that WSDK (the technical
+ preview of WSE) had A LOT of changes before it's initial
+ release!</b>
+ </ul>
+
<hr>
** Tools
**** Status
- The following tools are complete (mostly complete):
+ The following tools are complete (or mostly complete):
<ul>
* <code>secutil</code> is a tool to extract certificates and
strongnames from assemblies in a format that can be easily
(SPC) file - which is a long name for a simple PKCS#7 file.
* <code>makecert</code> to create X.509 test certificates that
- can be used (once transformed in SPC) to sign assemblies.
+ can be used (once transformed in SPC) to sign assemblies. It's
+ now possible to generate SSL certificates for web servers.
+
+ * <code>sn</code> is a clone of the <code>sn</code> to manage
+ strongnames. Current version can create, convert, sign and
+ verify strongnames signatures. Some configuration options
+ are still missing.
+
+ * <code>signcode</code> and <code>chktrust</code> for signing
+ and validating Authenticode(tm) signatures on assemblies (or
+ any PE file) are now working (signature and timestamps) but
+ some options aren't yet supported.
</ul>
Somewhat usable, somewhat incomplete:
<ul>
- * <code>sn</code> is a clone of the <code>sn</code> to manage
- strongnames. Current version is limited to creating new keypairs
- and converting values.
+ * <code>certview</code> is a certificate viewer for
+ <code>System.Windows.Forms</code> (right now only working on
+ Windows), while <code>gcertview</code> is the same viewer
+ implemented for GTK# (working on both Windows and Linux).
* <code>monosn</code> is a clone of the <code>sn</code> to manage
strongnames. This tools is part of the runtime (not the class
**** TODO
The following tools are still missing or largely incomplete:
<ul>
-
- * <code>signcode</code> and <code>chktrust</code> (in progress)
- for signing and validating Authenticode(tm) signatures on
- assemblies (or any PE file).
-
* Other tools like a, GUI-based, certificate manager...
</ul>
tools are of limited use until supported by the runtime.
<hr>
-** Other stuff
+** References
<ul>
- * SSL/TLS for secure communication (a prototype is under way).
- Some work is already visible in Mono.Security assembly (e.g.
- RC4, RSAManaged ...).
- </ul>
+ * RSA Laboratories' <a href="http://www.rsasecurity.com/rsalabs/faq/index.html">
+ Frequently Asked Questions</a> About Today's Cryptography, Version 4.1
+ * Public-Key Cryptography Standards (<a href="http://www.rsasecurity.com/rsalabs/pkcs/index.html">
+ PKCS</a>)
-<hr>
+ * National Institute of Standards and Technology - Federal
+ Information Processing Standards <a href="http://csrc.nist.gov/publications/fips/index.html">
+ NIST FIPS</a>
+ </ul>
+
+<hr>
** How to Help
<ul>
* Complete any of the TODO (and feel good about it ;-).
* Analyse the current coverage of the unit tests on the
- cryptographic classes and complete the unit tests.
+ cryptographic classes and complete the unit tests. <b><code>
+ monocov</code> does a great job at this! Now we just need to
+ complete the missing unit tests.</b>
* Optimization can also be done on most algorithms as crypto
is never fast enough. Some have been done using the
Community Edition of BoundChecker (a free VisualStudio
addon) - recommanded! Just be sure to test every optimization
- (using the unit test) carefully - it's so fast to break an
+ (using the unit tests) carefully - it's so fast to break an
algorithm ;-).
* Write some documentation on the cryptographic classes for
- the <a href="http://go-mono.com/tutorial/html/en/index.html">Mono
- Handbook</a> as I'm not a very good writer (at least in English).
+ <b>monodoc</b> as I'm not a very good writer (at least in English).
</ul>
Contact Sebastien Pouliot (<a href="mailto:spouliot@videotron.ca">home</a>
informations about the status of the cryptographic classes.
<hr>
-Last reviewed: June 11, 2003 (post mono 0.24)
+Last reviewed: October 26, 2003 (post mono 0.28)
projects / mono.git / blobdiff