what to do with a security freaked server? (7)

1 Name: Soyokaze!!N2wdD21j 2005-10-16 10:29 ID:fbhscDeT [Del]

I already bought the services for a year of a server, and without knowledge of their freaking cgi-bin policy.

Im having trouble for creating more then 1 board, because only has restrictions for use the scripts from the cgi-bin folder...

And im still trying to make some sense on them to let me use the scripts on any folder...

And because of that i had been forced to use futabally... scary...

But i hate it, it doesnt work like wakaba, that worked so much better...

Anything i can do about this issue?

2 Name: Soyokaze!!N2wdD21j 2005-10-16 10:46 ID:fbhscDeT [Del]

ahhh another thing, I got this problem

Software error:

install_driver(mysql) failed: Can't locate DBD/mysql.pm in @INC (@INC contains: . /usr/lib64/perl5/site_perl/5.8.6/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.5/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.4/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.3/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl /usr/lib64/perl5/vendor_perl/5.8.6/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.4/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.3/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl /usr/lib64/perl5/5.8.6/x86_64-linux-thread-multi /usr/lib/perl5/5.8.6) at (eval 280) line 3, <FILE> line 3.
Perhaps the DBD::mysql perl module hasn't been fully installed,
or perhaps the capitalisation of 'mysql' isn't right.
Available drivers: DBM, ExampleP, File, Proxy, Sponge.
at wakaba.pl line 45

3 Name: !WAHa.06x36 2005-10-16 11:59 ID:hFkAqqBA [Del]

It might be possible to hack Wakaba to run in one directory and keep its files elsewhere, but it requires some Perl skill. However, the second error seems to be because they haven't even bothered to install the Perl drivers for mysql at all. You could still use Kareha, but you'd have to hack that too, and really, it's pretty blatantly obvious this host is worse than Hitler.

I just had a silly idea, though. What if you install Kareha as if you could run it anywhere, and then put in a little script in /cgi-bin/ that just did something like:


chdir "/www/mypages/board/";
exec "kareha.pl";

4 Name: !WAHa.06x36 2005-10-16 13:20 ID:hFkAqqBA [Del]

On second thought, that won't work anyway. Scratch that.

The trick for getting Kareha running should be to put in a chdir "/server/path/to/html/files/" somewhere near the top, and then editing wakautils.pl to change one line:

'my ($path)=$ENV{SCRIPT_NAME}=~m!^(.*/)[^/]+$!;'.


'my $path="/web/path/to/html/files";'.

That might work. I haven't tested it, though.

5 Name: Soyokaze!!N2wdD21j 2005-10-16 19:55 ID:fbhscDeT [Del]

Okay, they just told me that they installed the drivers and that the code has problems... WHICH I WAS JUST LIKE "WTF ARE YOU SAYING?!?!!?!?!?!"

still i post here the log that they told me that they were having with wakaba.pl


/usr/bin/perl: symbol lookup error: /usr/lib64/perl5/site_perl/5.8.6/x86_64-linux-thread-multi/auto/DBD/mysql/mysql.so: undefined symbol: mysql_init
[Sun Oct 16 22:25:43 2005] [error] [client] Premature end of script headers: /home/np000399/public_html/cgi-bin/wakaba.pl


6 Name: dmpk2k!hinhT6kz2E 2005-10-16 20:21 ID:Heaven [Del]

Undefined symbols? Didn't they test it? Their problem seems to be a missing library. Tell them to do a "locate libmysql", and ensure the returned location is in the PATH. If it is, then it might be an issue of a different expected arch in each library (ie, one 32-bit, the other 64?).

Side comment for readers: never, ever sign up to a yearly contract without testing the host for a month or two before hand.

7 Name: test 2005-10-17 05:52 ID:Heaven [Del]

> and ensure the returned location is in the PATH.

Uh, make that LD_LIBRARY_PATH. I must have been asleep.

Name: Link:
Leave these fields empty (spam trap):
More options...