IL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, September 17, 2003 12:04 AM
Subject: How to secure database password? (was Re: Perl/DBI newbie: p
Zedgar,
You are chasing the yourself into circles. Security is dictated by
circumstances and resources available. In our case, we had plenty of
both and developed for our needs the "best" solution. Insofar as the
storing of the password for the login that is used to get the password,
we too
Hello,
Many thanks to R. Joseph Newton, Motherofperls, essential quint and Chuck Fox for
answering my questions, however it is still not what I was asking about. My previous
posts were long and maybe unclear so I'll try to get straight to the point this time,
adding more details at the bottom o
[EMAIL PROTECTED] wrote:
> Thank you Joseph and Motherofperls for your tips, however I need something more than
> security through obscurity, as this database is going to store our customers
> personal information (real name and contact information) which is absolutely
> unacceptable to be stor
andpoint.
Anyway, I'll leave go now... just thinking out loud... providing some food
for thought... etc...
Good luck!
quint
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Perl/DBI newbie: password storage / security question
Date: Sat, 13
R. Joseph Newton wrote:
> [EMAIL PROTECTED] wrote:
>
>>I'm basically concerned about the security of writing a simple web frontend to SQL
>>database, the most important question being: how should I store the database
>>password?
>>[...]
>>There are tens of websites on the server and every databa
