Michael Bell wrote:
Sorry, perhaps it is too late but I mean something different.
[...]
So the project could be divide into different aspects:(e.g. apps/x509.c). I don't like one big file OpenCA::Crypt::OpenSSL.
o Definition and document writing of the OpenCA::Crypto
interface and layered structure;
o Definition of the interface exported internally to the
different crypto providers ( OpenCA::Crypto ->
OpenCA::Crypto::OpenSSL);
o Development and validation of the OpenCA::Crypto and
feedback to the previous step;
o Implementation of the OpenCA::Crypto::OpenSSL module (having
different sub modules under the crypto vendor, i.e. OpenSSL::X509
... as pointed out by Julio);
Any ideas/opinions/suggestions ?
--
C'you,
Massimiliano Pala
--o-------------------------------------------------------------------------
Massimiliano Pala [OpenCA Project Manager] [EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.openca.org Tel.: +39 (0)59 270 094
http://openca.sourceforge.net Mobile: +39 (0)347 7222 365
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
OpenCA-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/openca-devel
