In response to questions posted off-list, I will explain how to implement a
"conf" file to increase security if you are using this script.

Change these lines in the script:

my $USERID = ''; # your reseller id
my $PASS   = '';        # your reseller password

to the following:

BEGIN {
      do "<path_to_this_file>/password_script.conf";
}


then create a file at the location above with the USERID/PASS lines you cut
from the script. Of course you should replace path_to_this_file with the
actual path. Then chmod 600 the password_script.conf file. This should make
your setup of this script a bit more secure.

-- 
John Keegan
[EMAIL PROTECTED]
http://RackShare.com


> From: John Keegan <[EMAIL PROTECTED]>
> Date: Mon, 24 Sep 2001 09:07:50 -0400
> To: "Doctor PC - Brian O'Donnell" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
> Subject: Re: password.cgi
> 
> Just had a look at this script and it seems there is an extraneous right
> bracket on Line 8, remove this and your script should work. Also make sure
> Line 18 is correct, the location of the "lib" directory relative to the
> script itself.
> 
> Also, make sure you have the Perl module Net::SSLeay installed on your
> server.
> 
> Lastly, I would say that you probably want to take the USERID/PASS variables
> OUT of this program, and put them into a separate "conf" file. Then set
> permissions accordingly on the conf file (ie allow the script to read it but
> no one else) then read in the conf file on start of the script.
> 
> Hope this helps anyone who has tried this send password script.
> 
> -- 
> John Keegan
> [EMAIL PROTECTED]
> http://RackShare.com
> 
> 
>> From: "Doctor PC - Brian O'Donnell" <[EMAIL PROTECTED]>
>> Date: Fri, 21 Sep 2001 00:28:45 -0400
>> To: <[EMAIL PROTECTED]>
>> Subject: password.cgi
>> 
>> Hello
>> 
>> I am new to this list. I am wondering if anyone has successfully installed
>> the password script found at http://www.opensrs.org/src/unsupported/ ?
>> 
>> I get an internal server error. I have checked all of the obvious things.
>> 
>> Thanks
>> 
>> Brian P. O'Donnell
>> Doctor PC
>> 
>> 
> 

Reply via email to