The PDBA toolkit has a password server.
http://www.oreilly.com/catalog/oracleperl
Jared
On Wed, 2004-03-10 at 11:11, Chuck Fox wrote:
> [EMAIL PROTECTED] wrote:
>
> >Hi there,
> >
> >I figured this would be a pretty common problem, but I didn't see
> >anything in the FAQ or docs.
> >
> >We've g
On Wednesday 10 Mar 2004 7:06 pm, News Reader wrote:
> On Wed, 10 Mar 2004 12:50:59 -0600, "Brad Fike" <[EMAIL PROTECTED]>
> said:
>
> Thanks for the ideas. I did try entering them in as blanks, but I still
> got this error:
>
> DBI->connect(BWEB) failed: [Microsoft][ODBC SQL Server Driver][SQL
> S
DSN, which other non-perl things use).
> If the user\pass is already in the DSN you should be able to just...
>
> my $db =
> DBI->connect("dbi:ODBC:$dsn","","");
>
>
> >-----Original Message-----
> >From: Sterin, Ilya (I.) [mailto:[E
[EMAIL PROTECTED] wrote:
Hi there,
I figured this would be a pretty common problem, but I didn't see
anything in the FAQ or docs.
We've got a script that uses DBI to connect to SQL Server.
There is a system DSN set up and this already has the username and
password. So do we really need to pass t
; >Sent: Wednesday, March 10, 2004 12:43 PM
> >To: [EMAIL PROTECTED]
> >Subject: RE: Avoiding coding username/password directly into
> >perl script
> >
> >
> >well, if your database requires a username/password, then you
> >can't just pass it the path
MAIL PROTECTED]
>Subject: RE: Avoiding coding username/password directly into
>perl script
>
>
>well, if your database requires a username/password, then you
>can't just pass it the path (DSN). Not even sure how you
>expect anyone to do that. I believe certain ODBC clients
You _do_ need to include the user name and password in the DBI connect
statement, but the way to make it more secure is to not hardcode those
in your scripts - create a Perl module in which you place variables that
_do_ contain the hardcoded values, but place that perl module in a
secure place on y
Hello
Try passing them in as blanks.
my $db = DBI->connect("dbi:ODBC:$dsn", '', '');
Peter
News Reader wrote:
Hi there,
I figured this would be a pretty common problem, but I didn't see
anything in the FAQ or docs.
We've got a script that uses DBI to connect to SQL Server.
There is a system
well, if your database requires a username/password, then you can't just pass it the
path (DSN). Not even sure how you expect anyone to do that. I believe certain ODBC
clients might have the capability to embed that either inside the DSN and/or somewhere
else on the system, so that when a cert
