Fail2ban is just another tool in your toolbox. Defense in depth, as others mentioned.
Fail2ban is primarily a tool to prevent brute force attacks, especially useful for services that don’t do their own throttling. For example I usually put ssh in fail2ban, but if Authelia’s built-in protection is good enough, then use that.
Outside ssh, anything that could be used to brute force credentials should be in fail2ban if they’re exposed: web sites with simple auth, mail, etc.
Yeah that’s my guess at well. Before I figured it out, I used a VPN connection into my local network (which works through hairpin NAT). I’m not a security expert, but that may be more secure than granting the permissions wholesale.
I had this happen too recently and only for certain apps. Turned out Android has a new permission that was being enforced: “Nearby devices”. Once I granted that to my browser, it could access my LAN again.
I think it’s fair to want a more helpful error message, but that’s not necessarily the purpose for path. There is a real cost to every entry in your $PATH. Not as much as in the world of spinning rust, but some.
There are some completion modules for shells that will suggest misspelled or even installable packages if it can’t find the command. Those are arguably better options.
As for traditional systems, I remember a time where running arbitrary commands, even with an --help argument could be dangerous and we had to set least try ‘man command’ first.
I thought this was how unix always has been? Sbin is for root binaries. It doesn’t make sense to include a bunch of commands you don’t have permission to execute in the path. I remember this being the case back in the 90s and didn’t realize it was no longer the norm.
Personally I’m less worried about them than me getting deported for my speeding ticket from 1999.
But yeah, the laws apply differently. The cruelty and injustice is the point.
The phrase “disqualifying crimes” did a lot of heavy lifting here. While some obvious ones will get you disqualified, e.g., murder, there are a number of less obvious ones, including minor drug offences and resisting arrest.
My motivation for calling for it to be the default was that it’s safer (in terms of data).
Another UX principle is that of least surprise. I think it’s reasonable to assume that most users will expect the copy to be fully complete when the dialog closes, and that they will be surprised when their files are corrupted. Changing the behavior in the desktop to delay closing the dialog until any copying to removable media is complete should not be a controversial change.
We’re seeing an influx of novice users to Linux. I don’t think we need a bunch “Linux ate my files” incidents if it can be avoided by a simple change, which itself can be easily reversed if you didn’t like it.
I would settle for checked-by-default “sync and wait” option. That way I can choose whether to cause a sync or not.
I wonder what the sampling/reporting issue is? Why Chinese specifically? Are there droves of Chinese gamers flip-flopping between Linux and Windows? That doesn’t seem likely.