[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re[2]: [vps-mail] Coding Question re Mailman script ... Never mind.
- Subject: Re[2]: [vps-mail] Coding Question re Mailman script ... Never mind.
- From: Abigail Marshall <abigail@xxxxxxxxxxxx>
- Date: Tue, 10 Feb 2004 12:56:05 -0800
JO> I am on the Verio VPS2, the -b option works flawlessly for me.
As I said in my posts, VPS1.
JO> You must have an existing user and password file to use
JO> this. And I am not on Apache 2.
You are correct, this option is included with at least some
versions of Apache 1.3... - but NOT on the VPS 1. I don't
know why - whether the VPS1 retains an older version of
htpasswd or Viaverio techs have modified it in someway for
security reasons - either one is plausible.
JO> Try it on your VPS1, just go into a temp folder if you
JO> wish, and create the file by "htpasswd -c .htpass test"
Thanks for the help and suggestions, John, but I did all of
this BEFORE I posted seeking help. It produced the
following error message:
> htpasswd -b test pword
> Usage: htpasswd [-cm] passwordfile username
> The -c flag creates a new file.
> The -m flag forces MD5 encryption of the password.
I have chased this down somewhat, though.
The default htpasswd for a VPS 1 is here:
/usr/local/bin/
15815 Oct 12 1999 htpasswd
However, there is a newer version available with the Apache
distribution:
/usr/local/apache/1.3.27/bin/
28288 Oct 14 2002 htpasswd
I copied that over to my ~/usr/bin/ directory and modified
the script to use that, and it DOES work.
But then, so does the Perl shell script I found, so I'm not
sure if it makes much of a difference.
Anyway, thanks for your input. I do think that this is just
one of many examples where the VPS2 environment is different
than the VPS1.
-Abigail
======================================================================
This is <vps-mail@xxxxxxxxxxxx> <http://www.perlcode.org/lists/>
Before posting a question, please search the archives (see above URL).
Main Index |
Thread Index