[27840] in Perl-Users-Digest
Perl-Users Digest, Issue: 9204 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Apr 26 18:05:50 2006
Date: Wed, 26 Apr 2006 15:05:07 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Wed, 26 Apr 2006 Volume: 10 Number: 9204
Today's topics:
generating passwords, base64, md5, or sha1 <dmehler26@woh.rr.com>
Re: Tracing SQL queries done via DBI (mod_perl) xhoster@gmail.com
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Wed, 26 Apr 2006 21:55:03 GMT
From: "Dave" <dmehler26@woh.rr.com>
Subject: generating passwords, base64, md5, or sha1
Message-Id: <X_R3g.23458$P2.2038@tornado.ohiordc.rr.com>
Hi,
I'm trying to get squid authentication working. I'm wanting to do either
basic or md5 passwords, for either htpasswd or htdigest both with apache
will do that, but i don't want to install apache just to get those programs.
So, what i was wondering, could i have a script that would prompt for a
username, password, and realm if the password type required it, then
appropriately encrypt the passwords, and store them in the designated output
file in the appropriate format?
Thanks.
Dave.
------------------------------
Date: 26 Apr 2006 21:46:31 GMT
From: xhoster@gmail.com
Subject: Re: Tracing SQL queries done via DBI (mod_perl)
Message-Id: <20060426180112.814$5p@newsreader.com>
Ignoramus8495 <ignoramus8495@NOSPAM.8495.invalid> wrote:
> > Ignoramus8495 <ignoramus8495@NOSPAM.8495.invalid> writes:
> >
> >> I would like to have a log of all SQL queries that my scripts do via
> >> DBI. (80k+ of perl code, mod_perl)
> >>
> >> I have one entry point (module) whose job is to give the database
> >> handle to everyone. So I have control over the handle.
Does it also give out statement handles or just database handles?
> >>
> >> There is a trace() method on DBI, however, it does not properly print
> >> the statements that were prepare'd a long time ago and are repeatedly
> >> execute'd.
> >>
> >> So... What am I missing?
If it only gives out database handles, then each CGI submission would have
to prepare the statement handles itself. So you shouldn't have cases where
you are executing things prepared a long time ago.
> I could possibly make some complicated analysis tool matching
> addresses of statement handles with previous output from prepare, but
> that would be a pain with obvious problems (several processes could
> have identical addresses occupied by different objects)
Does the trace output go through your logging methods? If so, have your
logger add a pid stamp to the output.
(if you set the trace level above 9, apparently this is automatically done,
but then you will get a lot more output)
Xho
--
-------------------- http://NewsReader.Com/ --------------------
Usenet Newsgroup Service $9.95/Month 30GB
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 9204
***************************************
