I use a (Perl) password server for this.
Passwords are stored encrypted in a configuration file.
Clients authenticate with the server, and receive a requested
password (encrypted) across the network, if the client is
entitled.
The user authentication is rudimentary, but it works.
SSH certificate
Greg Sabino Mullane wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
5. A better set of metadata for DBDs to report the functionality
they support. E.g., today, the only way to find out if a DBD
is threadsafe (at runtime) seems to be try it and hope for the best.
Could get_info be expa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> 5. A better set of metadata for DBDs to report the functionality
> they support. E.g., today, the only way to find out if a DBD
> is threadsafe (at runtime) seems to be try it and hope for the best.
Could get_info be expanded to include this?
> 8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
No time to respond fully, but a few cents here and there, with some
devil's advocate thrown in.
Darren Duncan wrote:
> All host parameters should be named (like ":foo") rather than
> positional (like "?"), meeting with the SQL:2003 standard. The na
Sam Vilain wrote:
> Maxim Sloyko wrote:
>
>> But this is not the point. The point was that usage of some file with
>> passwords by *DEFAULT* is not the way to go, IMHO. It raises more
>> problems than it solves.
>
>
> Can you give an example of such a problem that wasn't already there?
>
> J
When I go to the donation page and attempt to make a donation, the
drop-down box does not give DBI as a valid recipient. Is it possible
several people may not have donated as they noticed the same results, or
maybe they did and it all went into the Perl Development Fund instead?
> -Or
Ron Savage wrote:
On Thu, 07 Jul 2005 11:38:06 +1000, Daniel Kasak wrote:
Hi Daniel
my $sth = $dbh->prepate( "set dateformat dmy" );
What am I doing wrong?
probably "prepate" is not a function, I think you mean "prepare"
Does that exact query work via CLI interface (IE is the query bad)
Sam Vilain wrote:
Maxim Sloyko wrote:
But this is not the point. The point was that usage of some file with
passwords by *DEFAULT* is not the way to go, IMHO. It raises more
problems than it solves.
Can you give an example of such a problem that wasn't already there?
Just to be clear, the
