On Mon, Aug 27, 2001 at 07:06:58PM +0200, Massimiliano Pala wrote:
> This is a good idea. If you are planning of sending in a patch, use the latest
> version you find in the CVS ...
okay.
> 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.
hmm, that's right - it's the better way to but it there.
> 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 ???
hm, I'll think about that this night. But I'm not sure that I'll come up with
something usefull.
All I needed was the ability to see the openssl call and so I patched it
temporary into the version I use.
But I think a clean debugging interface is an important thing for such a module.
--
tschau , Uwe Gansert
-------------------------------------------------------------------------------
echo '$e=5;$p=3;$q=13;$h=$p*$q;while(($e*++$d)%($h-$p-$q+1)-1){};while($t=subst
r("82758c1b8939c7ef5c5d0같같같같같같같같같같같같같같같같같1eaa4aa38516aed5559fe
27fd0f5b0b464474b2316eac~~~~ [EMAIL PROTECTED] ~~~~390a03",$i,3)){$_.=pa
ck"I",(hex($t)%$h)**$d%$같같같같같같같같같같같같같같같같같h+95;s/_/ /g;$_=($i+=
3)%2?uc:lc;print"$_\n";}'|perl -ne"chomp;s/�|~|\s*ug@[^~]*//g;print"|perl
PGP signature
