Thankfully I have all of my themes on Mega.
And to everyone that took part in hacking the website: You're a dick.
And to everyone that took part in hacking the website: You're a dick.
Pretty understandable i think, the devs probably trusted everyone to not abuse their site and gave functionality a bigger priority then security.
In all seriousness now, might I suggest hiring an intern or someone to help educate the programmers on web application security? SQLi is really just the 101, there's more to consider (OWASP might be a good starting point), you'll definitely want to check this out now that you've established that, indeed, parts of your userbase are malicious and will abuse any and all flaws in your software.We know there is currently a security breach with our site, and we would like to let you know, that we are working tirelessly to fix this. We are deeply sorry for the inconvenience, and our site should be online again once we have solved it.
There is nothing wrong with MySQL, and i chose it above every other database type (however PostgreSQL is nice tooLesson 1 of network security: User input is untrusted and bad.
Avoiding SQL injections with prepared statements and the like, the way PDO would've offered, is trivial. Then again, you can't expect too much from people who still use MySQL as their database of choice and hook the website up with the MySQL root user.
If you need any help finding other unprotected parts, i've got some timeWe know there is currently a security breach with our site, and we would like to let you know, that we are working tirelessly to fix this. We are deeply sorry for the inconvenience, and our site should be online again once we have solved it.
Staff changes will be made, yes.In all seriousness now, might I suggest hiring an intern or someone to help educate the programmers on web application security? SQLi is really just the 101, there's more to consider (OWASP might be a good starting point), you'll definitely want to check this out now that you've established that, indeed, parts of your userbase are malicious and will abuse any and all flaws in your software.
StartSSL's revocation feees made for a nice disaster after Heartbleed indeed.Use http://startssl.com for free SSL certs too..
We were using StartSSL, with plans to upgrade to a paid certificate in the coming month after google paid out. Unfortunately, sometimes things like this get in the way, so until we fix the security hole and find the perpetrator, we will not be doing further upgrades (Obviously).You can apply for Let's Encrypt right now![]()
Will do, thanks for your recommendation.@GotKrypto67 OKEnsure that you escape characters, and don't use StartSSL when you can stop using it, request a better on through the beta request at
http://helloworld.letsencrypt.org
And use that
Give me 5 minutes with itso until we fix the security hole and find the perpetrator, we will not be doing further upgrades (Obviously).
After I finish some minor repairs here we may have to talk. Not sure just yet though. Ive followed you for further contact.Give me 5 minutes with it![]()
I doubt you can "find the perpetrator" in 5 minutes. I'm assuming @GotKrypto67 is considering legal action; locating someone isn't that easy. You'd probably need to notify the police, who may start a criminal procedure, from which you may then learn the identity of the perpetrator and only then you can sue for damages.Give me 5 minutes with it![]()
But finding the information to find the attacker is pretty easy. And from there, you email the ISP quoting the criminal damage and then go from there. If done by proxy, hope they keep logs. If done by TOR, you're out of luck.I doubt you can "find the perpetrator" in 5 minutes. I'm assuming @GotKrypto67 is considering legal action; locating someone isn't that easy. You'd probably need to notify the police, who may start a criminal procedure, from which you may then learn the identity of the perpetrator and only then you can sue for damages.