I have a domain with a few forwarding email accounts that forward to mac.com email accounts... for some reason every once in a while these accounts stop working...
This is the error I get when I email to that account:
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: ...
A client's server's password was guessed, and the hacker conveniently uninstalled perl. I can't seem to get perl reinstalled. Any ideas on how this would be done? RPM, TAR's and YUM don't work, as they require perl!
all we know that perl language its using in alot of scripts and alot of system admins stop it why this why u dont try stopp the problems from it and make ur client have perl to used it in scripts lets try this if some one need to see passwd he will do cat /etc/passwd what about make this chmod 700 /bin/cat and he will used wget to get files what about this chmod 700 /usr/bin/wget and lynx what about chmod 700 /usr/bin/lynx in this case we make root only can using this commands any system admin sure know now the idea and he can use it as he want ,, this secured method not only in perl its in another programing language put i give this as a clear exampel.
I have a Centos VPS with Cpanel. I have begun receiving some email notifications, apparantly from my cpanel... The latest one says that the version of perl I am running is too old.
Subj: [checkperlmodules] perl version too old (v5.8.8 required, v5.8.7 is installed.)
Are there any problems or dire consequences from upgrading or side effects? What version should I upgrade to?
ive been trying to install it for about 3 hours and ive finally got it working. now, how do i configure it to be nice and secure?
first thing is that i want to restrict which paths people can use in scripts. my site needs to access any paths but site users can only access their own directories. i want the exact same thing as in this thread but with perl instead of php
how do i block certain functions and which ones do i block? i heard perl and php are very similar so im guessing i want to block similar functions to the ones listed here
Code: PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 9488 nobody 25 0 1612 1280 1108 S 21.1 0.2 619:37 1 perl bodyb3 200.101.193.42 0 5000 I also ran netstat -n and found this: Code: udp 15184 0 server.host.com:55936 ns1.datacenter.net:domain ESTABLISHED
Testing connection speed...(this could take a while)...Done Ping:2.016 Testing connection speed to cpan.erlbaum.net using pureperl...(157450.00 bytes/s)...Done Ping:2.316 Testing connection speed to cpan.belfry.net using pureperl...(157450.00 bytes/s)...Done Ping:1.911 Testing connection speed to cpan.glines.org using pureperl...(104300.00 bytes/s)...Done Three usable mirrors located Mirror Check passed for cpan.erlbaum.net (/index.html) Unknown config variable 'less' commit: wrote '/usr/lib/perl5/5.8.8/CPAN/Config.pm' CPAN: File::HomeDir loaded ok (v0.65) CPAN: Storable loaded ok (v2.16) Going to read /home/.cpan/Metadata Database was generated on Wed, 15 Aug 2007 01:38:08 GMT Acme:pork is up to date (0.0.7). perlmod--Install done
I've used Servage for about 18 months. For most of that time there have been no problems. Then they decided to upgrade the cluster. This happened 3 weeks ago. Since then, there has been a catalogue of problems, mostly centred around a Perl script my site uses to implement a wiki.
The first problem was that they had removed four of the supporting Perl modules used by my Perl script. All of the missing modules are ones you would expect to find on any server that claims to support Perl. They had warned that this might happen (obviously too difficult for them to make sure that the upgraded server has all the Perl modules) so I notified them with a list of missing modules expecting the modules to be restored quickly. It actually took 1 week, during which time their support team tried their best to annoy me by giving responses related to PHP (apparently they'd managed to kill PHP scripting completely) and a non-working link to a list of installed modules (I knew what was installed already).
Having now got the script running, I hit a further problem. Prior to the upgrade the script had run under the "webserver" account. It was now running under the "you" account. This meant it couldn't write to its own data files. I had real trouble getting Servage to understand this one, let alone fix it. Most of their answers were about how to change the ownership of my script, which makes absolutely no difference to the problem. Eventually, after 4 days, they tried to fix the problem. The result was that my website became completely inaccessible. Even the static content was giving a 403 error. Again, it took support a while to understand the problem and about 1.5 days to fix it.
At this point Servage claimed to have fixed all outstanding issues. However, my script was still running under the wrong account. In frustration, I changed the ownership of all the script's data files to "you", which at least got my wiki running again.
However, I now find that people can't upload images to the site. Any attempt to do so produces an error "CGI open of tmpfile: Permission denied".
I've given up. I think my chances of getting Servage to even understand the problem are minimal. I'm not even going to try. I will be moving to another host as soon as possible - probably a VPS. That way I should be able to fix most problems myself.
we have a customer who has Red Hat Enterprise Linux 4 on there server and they have asked us to install GD-1.8 and perl-GD-1.33-1.i386 every time we try and install GD-1.8 it says 'GD-2.2 is newer blah blah' and we can not continue. Dose any one know how this can be done and if so could they please give us some information of how to do it.
we have been thinking about forcing 1.8 to install but we do not think this is a good solution as it will cause other problems.
i've to install perl-XML-Parser on my dedicated server. i'm using centOS4.5. i tried
Code: yum install perl-XML-Parser after that command i got:
Code: Setting up Install Process Setting up repositories Reading repository metadata in from local files Excluding Packages in global exclude list Finished Parsing package install arguments No Match for argument: perl-XML-Parser Nothing to do
if anyone asks why i've to install it, i want to install VNC. while installing gnome with that command:
Code: yum install gnome* i got that error :
Code: --> Running transaction check --> Processing Dependency: perl-XML-Parser for package: intltool --> Finished Dependency Resolution Error: Missing Dependency: perl-XML-Parser is needed by package intltool
so, i think that i've to install perl-XML-Parser. but how?
find my server filled with suspicious perl processes, most likely the result of bad PHP coding somewhere on my box. I successfully eradicated all of it, but I know it'll only come back again unless I figure out where it came from. Anyone have any ideas how to track it down? I'd search all the httpd logs for each domain, but I don't really know what I'd be looking for.
That's what it usually looks like. Anyway, more and more Ws were added in a matter of seconds as I watched it. Next thing, my site doesn't load, and it goes dead. My TimeOut in apache was set to 5 seconds. Now it's at 2, though. I do have keep alive on, but it is VERY low, like its set to 2 seconds and the max keep alives is set to 15 or so.
I have been working on even just catching who is doing this for about 2 weeks now, trying everything to my ability. Here is everything from start to finish:
1. First I tried mod_evasive - this program seems worthless, it doesn't ever detect anything. I can post settings if need be, but ive played with it and it just doesn't work well I find. I have more trouble with it getting false positives. Also, I tried going over the apache logs. For me, this has been a nightmare because its just so hard to see between attackers and non attackers... and i've come up with nothing.
2. I tried APF with AntiDOS but it didn't seem to do anything...
3. I read about DDoS deflate by medialayer, and installed it and gave it a shot. It didn't do anything for me. I tried poking around with the command they have on their website and I found the results quite weird, it didnt show me all of the IPs like it was supposed to, but rather some mess like:
Code: 1 (ip here) 3 (ip here) 9 (1 addres ses) So I did more searches online, and eventually came across this command:
Code: netstat -ntu | grep ':' | awk '{print $5}' | awk '{sub("::ffff:","");print}' | cut -f1 -d ':' | sort | uniq -c | sort -nr This seemed nice, looked like it was working as it should this time. I used the test.pl ( my only test for this, I have trouble finding other tools )that comes with mod_evasive and sure enough it showed connections by me in there about like 150 or so after. I thought, 'hey thats pretty good, now ill try to make a script to parse it.' I did this, and then croned the script to run every minute.
Then I asked a friend of mine who I know has a better "DoS"er (though won't give it to anyone, understandably) to test the defence. It didn't hold up well at all. He suggested making the script run in an infinite loop instead of a cron, and make it sleep in the loop forever.
I did just that, and it now runs every 5 seconds. Here is the script, it's not the best, but it's all I've got now:
This actually worked; he started his attack, it found his IP, and he was blocked, and I didn't go down. The netstat command showed him in with some 200 something connections before he was blocked.
I was not able to see if this was effective against this issue until today, haven't been hit for 4 days now or so (perhaps some sort of easter vacation?). Today though, I watched the same thing happen again, filled to the brim with Ws.
The netstat command I found doesn't seem to be helping me here. If I am correct:
W means Sending Reply, according to the server status page. So what's going on here, someones making lots of connections and my system can't send a reply back for some reason?
My main questions are,
1. Am I right, that this is some kind of DoS?
2. If yes, how is this being done? And are there any test scripts available that I can download and try on myself to watch the statistics & test some more?
3. And again, how can I go about detecting whatever this is? Maybe some better netstat command, or something I can look for on the command page?
4. Is there any way to improve my perl script to protect against this?
5. If it isn't a DoS attack, what else might it be?