[Mono-list] Crypto Unit tests on linux
Sebastien Pouliot <firstname.lastname@example.org>
Wed, 16 Oct 2002 18:30:53 -0400
Thanks for all three options.
> 1) write a small xml parser that handles just the stuff you need in corlib
> 2) (better, IMHO) write an internalcall that uses the GMarkup parser
> in glib and fills in the RSA and DSA structures.
> > 3) use: Assembly.Load, Activator.CreateInstance & MethodInfo.Invoke
I would find the reflection stuff much easier but Paolo has a good point.
I've participated in the design and implementation of a hardware token which
included crypto, smart cards and biometry (and I even looked at how we could
get a JVM into that box). I know that I would have hated any design that
didn't minimize dependencies as much as possible (as such design are often
very limited on memory space).
However I would like very much, if possible, that the crypto classes to be
implemented using 100% managed code and I know that some other classes are
gonna require a lightweigth XML parser (probably CryptoConfig but I've not
finished looking at the System.Configuration classes).
So I will put the small parser on my todo list (unless someone else is
interested :-) and comment the current "bad" code so the tests (and classes)
can be compiled back into mono.
Security Architect, Motus Technologies, http://www.motus.com/