News for hackers. Stuff that matters.
Re:Why Self-Host? by virtue3 on Thursday October 09, 2025 @02:08PM (#45531077)
I used digital ocean for hosting a wordpress blog.

It got attacked pretty regularly.

I would never host an open server from my own home network for sure.

This is the main value add I see in cloud deployments -> os patching, security, trivial stuff I don't want to have to deal with on the regular but it's super important.

Re:Why Self-Host? by tadfisher on Thursday October 09, 2025 @02:18PM (#45531210)
Wordpress is just low-hanging fruit for attackers. Ideally the default behavior should be to expose /wp-admin on a completely separate network, behind a VPN, but no one does that, so you have to run fail2ban or similar to stop the flood of /wp-admin/admin.php requests in your logs, and deal with Wordpress CVEs and updates.

More ideal: don't run Wordpress. A static site doesn't execute code on your server and can't be used as an attack vector. They are also perfectly cacheable via your CDN of choice (Cloudflare, whatever).

Re:Why Self-Host? by manmal on Thursday October 09, 2025 @04:39PM (#45532815)
A static site does run on a web server.
Re:Why Self-Host? by moehm on Thursday October 09, 2025 @06:10PM (#45533629)
Yes, but the web server is just reading files from disk and not invoking an application server. So if you keep your web server up to date, you are at a much lesser risk than if you would also have to keep your application + programming environment secure.
Re:Why Self-Host? by manmal on Friday October 10, 2025 @04:55AM (#45536659)
That really depends on the web server, and the web app you'd otherwise be writing. If it's a shitty static web server, than a JVM or BEAM based web app might be safer actually.
Re:Why Self-Host? by moehm on Friday October 10, 2025 @08:42AM (#45538329)
Uh, yeah, I thought about Nginx or Apache and would expect them to be more secure then your average self-written application.
Re:Why Self-Host? by rrix2 on Thursday October 09, 2025 @06:07PM (#45533599)
a static site is served by a webserver, but the software to generate it runs elsewhere.
Re:Why Self-Host? by manmal on Friday October 10, 2025 @04:56AM (#45536666)
Yes. And a web server has an attack surface, no?
Re:Why Self-Host? by mikepurvis on Friday October 10, 2025 @07:51AM (#45537848)
I think it’s reasonable to understand that nginx/caddy serving static files (or better yet a public s3 bucket doing so) is way, way less of a risk than a dynamic application.
Re:Why Self-Host? by manmal on Friday October 10, 2025 @08:01AM (#45537946)
Of course, that’s true for those web servers. If kept up to date. If not, the attack surface is actually huge because exploits are well known.
Re:Why Self-Host? by 63stack on Friday October 10, 2025 @04:11PM (#45543251)
What are these huge attack surfaces that you are talking about? Any links?
Re:Why Self-Host? by codegeek on Thursday October 09, 2025 @02:35PM (#45531397)
The thing with WordPress is that it increases the attack area using shitty plugins. If I have a WP site, I change wp-config.php with this line:

    define( 'DISALLOW_FILE_EDIT', true );
This one config will save you lot of headaches. It will disable any theme/plugin changes from the admin dashboard and ensures that no one can write to the codebase directly unless you have access to the actual server.