Search results

Incoming and outcoming connections to the database are rejected, so no. Closest thing you could have is to have a PHP script on your site that can handle the requests from the external python script.

Please refer to this: http://stackoverflow.com/questions/13990557/php-file-get-contents-from-url-with-port

Try re-adding the domain.

As this is shared hosting, nothing. Only the people who are able to modify/manage the server(s) are able to do the appropriate tweaks to reduce how often this happens.

I would say no, unless you want every other site to be affected. The Varnish Cache Server is a little bit like a web server but it's a "pass-thru" acting similarly to a reverse proxy. When you use that line to disable Varnish Caching, that's just an option for Varnish. It would have caching...

So there's none in the spam folder?

Use this: https://x10hosting.com/sso/login/forgotten

The PHP vulnerability could be a lie (even though that wouldn't be a surprise). They have not taken security seriously for many years, didn't show any care since the first report and they were trying to hide it for a bit. So, I don't see why I should trust them. Fact is that the data is out and...

Unfortunately there are some vague spots as of now. 000webhost should know if their server log had logged the attack and of course the dumper should also know. Because of the fact that they had been trying to cover it up longer than it had to, I would look around and not just rely on the...

You should know 000webhost has been trying to be vague with the details. 'lol.txt' was deleted and so it's getting a HTTP response of 301 resulting in the browser pointing towards that main page. The screenshot I did is the store that's selling such data.

You're allowed to create and use a .htaccess file.

Well, there's this...

But were they any after March and before October?

Give this a shot: https://x10hosting.com/support/general/varnish-cache

1. I'm sure that there's more too, but why not try lowering the amount? 2. That doesn't seem to be the case, according to Troy's article. If you weren't in the first dump and got your account deleted before the second then you wouldn't be on the second one.

This is likely due to Varnish Cache (server-side caching). You could disable this for your site if you frequently update it, though it's recommended to have it enabled when you're done and it's ready for the outside world. You could either wait the server-side cache to expire or disable...

Good catch. I had researched a crazy amount of stuff (mostly from the original article that's very detailed) and currently in the process of getting CF to stop servicing the site that is selling the user credentials in plaintext. If you had created an account March 2015, earlier, or October...

To expand the answer, allowing you to use functions like exec() is like allowing SSH access. This is free web shared hosting so people can end up performing malicious tasks on te entire server holding many accounts if it were to be enabled. And we're talking about anyone. There's a lot more to...

It's not showing the error I expected to see, though it's very related to it. There's a large possibility that the script was sending a POST request, returned a 403 and WordPress failed to handle the failure (looks like there's only .success()). Getting right to the point, mod_security is...

PHP7 is NOT ready to be used on production servers. Having PHP7 installed and being used before the final stable release can introduce very nasty issues such as potential memory leaks and critical security issues which could affect the whole server. It is only to be used for servers not used in...