Uwe Gansert wrote:
>
> Hi,
Hi,
> after playing around with the OpenCA::* perl modules I wished for some kind of
> debugging option that let me see the executed openssl command with all
> parameters.
Indeed I used to write debugging code and then delete it before the releasing
time so as not to have to worry about its 'elegance'.
> What do you think about that ? I would implement such kind of code, if you
> are not totally against it, and send you the patch.
This is a good idea. If you are planning of sending in a patch, use the latest
version you find in the CVS ...
> I thought about something like a bitmask for debugging. Like :
>
> my $openssl = new OpenCA::Openssl( DEBUG => 1 );
If you add the parameter to the setParams function you can either set the
debugging
level non only when creating a new istance of the module.
Also we could think of some kind of debugging-level standardization:
0 - No debug
1 - Info debug
2 - Daemon debug
3 - Full debug
or something like this. Some has debugging-level description proposal ???
> Would that be okay for you ?
:-D I am always happy with good Ideas...
--
C'you,
Massimiliano Pala
--o-------------------------------------------------------------------------
Massimiliano Pala [OpenCA Project Manager] [EMAIL PROTECTED]
[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
