Search results

Hello ddezine, Yes they are! __________________ Added after 5 minutes: Please feel free to drop by live chat if you have any questions

BigScoots.com is a well known leader in the premium hosting community. With Cisco networking equipment, owned enterprise grade servers and our widely renowned management approach, people know what to expect when they go with BigScoots. To give you a little peak into who we are, we are delighted...

BigScoots.com is a Chicago based hosting provider. We offer shared, reseller, VPS, Hybrid VPS, Dedicated and colocation. We have recently put together some very cheap budget plans that are perfect for just about anyone. The best part is they still come with basic support so if you are in need...

What did the hacker do exactly? Did he just embed code into your html? What CMS are you running if any. Did any of your directories/files need to be chmod'd?

He has a VPS so for his host to block SSH would be extremely unlikely, wouldn't make sense. As for his ISP, still doesn't make sense as to why but more believable than his host.

That's if FTP will allow him to log in as root, as far as I know Kloxo does not by default.

root@stewie [/rar]# make mkdir -p /usr/local/bin mkdir -p /usr/local/lib cp rar unrar /usr/local/bin cp rarfiles.lst /etc cp default.sfx /usr/local/lib root@stewie [/rar]# make install mkdir -p /usr/local/bin mkdir -p /usr/local/lib cp rar unrar /usr/local/bin cp rarfiles.lst /etc cp...

Alright, that looks fine, however what did the box respond with after running that? *More so after the make and make install commands.

That is not an error.

There are many different ways a hacker could of got in apart from it being your hosts fault. .htaccess will affect every sub-directory after the directory you actually place it in. If you want your whole site to be affected by it then you would put it in your root web directory such as...

Can you screen shot or copy/paste the error when you run the command? Also, what is the filename including the extension

WinSCP would still be connecting to port 22 if the VPS is using the default port and if the problem really is the ISP blocking it(which is very strange) then best bet is to change the default ssh port.

I've never heard of a ISP blocking port 22 for SSH. I would ask your provider to change your SSH port then, its very simple and they shouldn't have any problem doing it. Otherwise PM me and Ill help ya out.