[ale] How to get working htpasswd command onto old GoDaddy Server

[Jim Kinney]

Be aware that perl crypt only uses the first 8 characters of the user
supplied password.
CPAN Apache-htpasswd may be a better solution
On Fri, 2017-02-03 at 11:11 -0500, Neal Rhodes wrote:
> hmm.  Sometimes just asking a question provokes an answer.  
> Apparently this little bit of PERL will create a similar file. 
> 
> 
> 
> cat myhtpasswd.pl
> 
> #!/usr/bin/perl
> 
> use strict;
> 
> chomp(my $filename=$ARGV[0]);
> 
> chomp(my $username=$ARGV[1]);
> 
> chomp(my $password=$ARGV[2]);
> 
> if (!$filename || !$username || !$password) {
> 
>   print "USAGE: ./crypt.pl filename username password\n\n";
> 
> } else {
> 
>   open FILE, ">>", $filename or die $!;
> 
>   print FILE $username . ":" . crypt($password, $username) . "\n";
> 
>   close FILE or die $!;
> 
> }
> 
> 
> 
> The actual encrypted string is completely different from what my
> Centos box generates, but when I plopped it in place, Apache accepted
> the very same password. 
> 
> 
> 
> 
> 
> On Fri, 2017-02-03 at 10:53 -0500, Neal Rhodes wrote:
> 
> >     So, we have a hosting account on a Godaddy Linux server: 
> > 
> >     
> > 
> >     Linux XXXXXXXX.secureserver.net 2.6.18-411.el5PAE #1 SMP Mon
> > Jul 11 18:26:16 CDT 2016 i686 i686 i386 GNU/Linux
> > 
> >     
> > 
> >     Which, amongst other things, hosts the Lloyd Shaw Foundations
> > historic music downloads.   So people all over the world are paying
> > a tiny amount for tunes from the archives via Paypal, and then I
> > setup download for them. 
> > 
> >     
> > 
> >     Which now has me building an .htpasswd file on my local Centos
> > 6 64 bit system, and shoving that over via scp. 
> > 
> >     
> > 
> >     Because the Godaddy server lacks an htpasswd command.    And
> > Godaddy support has in the past and continues to decline to provide
> > a compatible one.  
> > 
> >     
> > 
> >     BUT, they don't have any problem with me stuffing one there in
> > my local ./bin folder and running it.    So, if I could find a
> > compatible binary to the above, I could put the entire fulfillment
> > process in one place and put a PHP front end on it and allow
> > volunteers other than me to do it in places other than my office. 
> > 
> >     
> > 
> >     So, the htpasswd from my 64 bit Centos 6 server didn't fly - I
> > assume the binary is incompatible.   How would I go about finding a
> > compatible one?   I did some random digging with rpmseek.com, and
> > found one in  HTPASSWD-APACHE-2.2.22-7.I486.RPM, but after
> > unpacking and shoveling it over there, it wants some libraries: 
> > 
> >     
> > 
> >     
> >         ./htpasswd: error while loading shared libraries:
> > libaprutil-1.so.0: cannot open shared object file: No such file or
> > directory
> > 
> >         
> > 
> >     
> >     Obviously, getting shared libraries starts to get more
> > involved.   I just want to create a one-line ..htpasswd file Apache
> > is happy with for each music download directory. 
> > 
> >     
> > 
> >     If this takes a lot of drama, I might just accelerate the
> > migration of my hosting off this server onto a more current one,
> > which Godaddy says they have to force to happen anyway by the end
> > of 2017. 
> > 
> >     
> > 
> >     Regards, 
> > 
> >     
> > 
> >     Neal 
> > _______________________________________________
> > Ale mailing list
> > Ale at ale.org
> > http://mail.ale.org/mailman/listinfo/ale
> > See JOBS, ANNOUNCE and SCHOOLS lists at
> > http://mail.ale.org/mailman/listinfo
> > 
> 
> 
> 
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
-- 
James P. Kinney III

Every time you stop a school, you will have to build a jail. What you
gain at one end you lose at the other. It's like feeding a dog on his
own tail. It won't fatten the dog.
- Speech 11/23/1900 Mark Twain

http://heretothereideas.blogspot.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20170203/df453cb8/attachment.html>