

Yeah, they never are. Scientific conclusions are generally a lot more nuanced and cautious than what this guy’s claiming. He only read headlines.


Yeah, they never are. Scientific conclusions are generally a lot more nuanced and cautious than what this guy’s claiming. He only read headlines.


Kids have no idea what a “boomer” is.


the problem with systemd taking over anything also has to do with it offering options that actually lessens efforts
You systemd haters are practically feral. WTF does this have to do with systemd?


deleted by creator


OMG.
https://en.wikipedia.org/wiki/Security_through_obscurity
In security engineering, security through obscurity is the practice of concealing the details or mechanisms of a system to enhance its security. This approach relies on the principle of hiding something in plain sight, akin to a magician’s sleight of hand or the use of camouflage. It diverges from traditional security methods, such as physical locks, and is more about obscuring information or characteristics to deter potential threats. Examples of this practice include disguising sensitive information within commonplace items, like a piece of paper in a book, or altering digital footprints, such as spoofing a web browser’s version number. While not a standalone solution, security through obscurity can complement other security measures in certain scenarios.
You don’t know what you’re talking about - please stop. It’s embarrassing. It’s a long-standing industry term not some weird phrase I just made up. Nobody is saying “Linux is obscure”.


Enjoy your “security”. 🙄


Sorry - which part of your comment added anything of value? “can help to minimize the attack surface”? 99% of the time a proxy just passes traffic through. Unless you’re talking about a WAF which is a) a different thing and b) NOT what any home gamers are talking about when they recommend nginx, traefik, etc. to newbs.


Just google the term next time rather than embarrassing yourself.
You can dislike systemd, its6okay. But there’s no need to be stupid about it.
Yes - things built to work with systemd… require systemd to work.
But you don’t need to use all the systemd services. You can use other tools. Because systemd is not a monolith.


See what I mean?
As if a proxy blindly passing traffic directly to a backend server “reduces attack surface” in any meaningful way. 🙄
Edit: Guy edits his post with a bunch of stuff and assumes I’ve read it later. I can’t eyeroll enough…
Systemd is feature-rich but controversial. Its monolithic design bundles service management, logging, networking, device management, and more into a single codebase exceeding 1.4 million lines of code.
That is a gross misrepresentation of systemd…
It’s like saying GNU coreutils is monolithic because all of the individual tools combined are bundled together.
Systemd is comprised of many individual applications.


Newbies will ask stupid questions, that’s not their fault.
The people answering should know better than to answer with their favorite distros.
The correct answer is “pick a popular one and don’t worry about the differences, you’re too inexperienced to notice them anyway.”


The self-hosted crowd thinks reverse proxies protect you from the Internet. Don’t expect too much of them.


You could have just said that you don’t know what “security through obscurity” is.


It goes right to the top!


To be fair - it has gotten a lot better in the last few years. For a while though it was super frustrating.


2.5’ hdd but besides running tight on space
No wonder - that’s huge! (sorry - couldn’t resist)
While I don’t exactly intend to run RAID
At these sizes you may want to consider it - at least a mirror (RAID1). That’s a lot of data to lose and/or have to fetch from backups. Being able to limp along until you get a replacement is an enormous time-saver.


Underrated comment.
A “howto” that just gives you scripts and commands to run is pointless. You need to understand the technology, and networking in particular.


No?
Your perfamatry is quite obliqueto.
Language is fluid.