Michael Bell wrote:
> I have to generate some files for the RBAC (not CBAC!!! - what is CBAC?)
> the rest looks ok.
Ok. (Sorry, CBAC is a CISCO IOS option... :-( )
> That's correct. First we need five additional databases:
> * RBAC
> * PENDING_CRR
> * APPROVED_CRR
> * ARCHIVIED_CRR (is archivied correct?)
> * DELETED_CRR
I will add to the DB module too, then.
> > Also I need a list of the currently used modules having the SNAPs to
> > install (at least this!) fine.
>
> DBI, DBIS, RBAC
The DBI is equivalent to the DB module, the RBAC manages roles, what's
DBIS for ?
> > Modules documentation will be installed by single module installation
> > procedure - so the 'make install' for each module will install the POD
> > documentation you can add to the end of the module source code.
>
> I don't like to store the documentation directly in the sourcecode. Is
> there another solution to store the POD-docs for the perlmodules?
Unfortunately no. It is a standard PERL module procedure and it would be
best if we follow it - so the standard "make Makefile.PL; make ; make
install" sequence will be followed. This is required to have our modules
onto CPAN too.
[openca-docs]
> Listen quite good. Who write it ;-D
Who knows ??? :-D When code will be stable we'll assign work about docs.
> > Just the last thing: I need all the .conf options for your modules
> > (DBI, CBAC, etc... ) and the status of the signing daemon.
>
> This will take some time to check all my conf-files.
Let me know, I am waiting for it to update the CVS config files.
> Could you establish a second page beside the about-page where you
> publish all actual developers? I was a little bit surprised about the
> comment of Eric Bergeron who mails a comment to a bug that he works on
> the OpenCA::OpenSSL module as an OpenCA-developer.
I will. We have been in contact with a few mails but it has been added
as a developer not much time ago. He is in charge of keeping up-to-date
the OpenCA::OpenSSL module with the openssl options as well as trying
to use the IPC module for interprocess communication instead of the
system calls to improve reliability.
> Did we ever announce the official usage of the bugtrackingsystem of
> sourceforge?
I have updated all the links onto the web-site including references
to the bug-tracking system (check the support section).
--
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
S/MIME Cryptographic Signature
