Because you pointed 2 programs at the same directory to sync the content with an external directory structure.

In my experience adding an already existing directory structure to a sync program is a bad idea. Create the directory and then move the existing structure into it to be safe or/and at the very least have a backup.

Not having a backup is on you. You got lucky this time.

NOTE: Scrutiny is a Work-in-Progress and still has some rough edges.

Honestly, at this point i would not recommend the usage of scrutiny, the development was almost ways really slow and the creater does not seem to have kuch interest in the project. There are still standing issues and imho important features missing.

I would look into prometheus+grafana or something of that sort.

You have clearly not understood what it does. It basically acts as a basic WAF by blocking the access to various paths that are required by the default sharing feature but not by this “proxy”.

I mean you have the current image cached on the local server when you use it.

1 GB of RAM for every TB of storage is recommended but you can do with way less for ZFS.

What do you mean with encryption? Does it need to be transport encrypted, end to end encrypted or is encryption at rest (when the server is offline) good enough?

Yes i do i and you do you. But advertising those things as security measures while not adding any real security is just snake oil and can result in neglecting real security measures.

As i said, the whole internet can be port scanned within seconds, so your services will be discovered, what is the risk you assume to have when your IP address is known and the fact that you host a service with it? The service has the same vulnerabilities if it is hosted via cloudflare tunnels or directly via port forwarding on the router. So you assume that your router is not secure? Then unplug it, cause it is already connected to the router.

Geoblocking is useless for any threat actor. You can get access to VPN services or a VPS for very very very little money.

2. Guess what, all IP addresses are known. There is no secret behind them. And you can scan all IPv4 addreses for ports in a few seconds at most.
3. So some countries are more dangerous than others? Secure your network and service and keep them up to date, then you do not have to rely on nonsense geoblocking.
4. Known bots are also no issue most of the time. They are just bots. They usually target a decade old Vulnerabilities and try out default passwords. If you follow my advice on 3. this is a non issue

You want your backup functional even if the system is compromised so yes another system is required for that, or through it to the cloud. Important that you do not allow deleting or editing of the backup even if the credentials used for backing up are compromised. Basically an append only storage.

Most Cloud Storage like S3 Amazon (or most other S3 compatible providers like backblaze) offer such a setting.

I doubt that this is the case, whether it is encrypted or not. The complexity and risks involved with decrypting it on the fly is really unrealistic and unheard of by me (have not heard of everything but still)

Also the ransomware would also need to differentiate between the user and the backup program. When you do differentiated backups(like restic) with some monitoring you also would notice the huge size of the new data that gets pushed to your repo.

Edit: The important thing about your backup is, to protect it against overwrites and deletes and have different admin credentials that are not managed by the AD or ldap of the server that gets backed up.

During that time, your data is encrypted but you don’t know because when you open a file, your computer decrypts it and shows you what you expect to see.

First time i hear of that. You sure? Would be really risky since you basically need to hijack the complete Filesystem communication to do that. Also for that to work you would need the private and public key of the encryption on the system on run time. Really risky and unlikely that this is the case imho.

You should have read the post more carefully. The CVE affects every OS. Just the first shown example is Windows only.

Also, the relevant commits are outlined in the first paragraph. This article is not for the stupid user it’s a technical analysis on a few ways to exploit it and for those cases the commits are more relevant than the version. Also saying which versions are affected is not that easy, commits can be backported into an older version by for example the packager.

This is not really correct. Those companies take complete control of the secret keys. And no, it is not the same effect when you use tailscale compared to wireguard cause of various reasons. CGNAT, no port forwarding, funnels etc.

Netmaker, Tailscale or Zerotier

No way in hell i am giving a company complete remote access to my servers and clients.

Really disliking that discord is used as helpdesk/forum. Not really searchable via the web.

Also no link to the repo.

Have found it by accident too. Just amazing.

Would love something like that for the Desktop. Basically a Cockpit+Serverbox+xpipe for my desktop clients.

Nuclear power does not solve the issue here. Nuclear reactors take hours or even days to ramp up or down. They are not quick enough to react to such occasions.

No it is not. If you calculate in the future money tax payers have to pay to keep the nuclear waste safe (for thousands of years) or the cost of a larger incident like Chernobyl or Fukushima which also has to be paid by the tax payers then the ‘cheap nuklear power’ is not so cheap as it looks like…

Who the hell is pulling the docker-compise.yml automatically every release? I find myself already crazy by pulling the latest release but the compose file is just a disaster waiting to happen.

How do you even encrypt a server so that it doesn’t require human intervention every time it goes down/restarts?

The only time my Server goes down, is when i manually reboot it. So waiting a minute or two, to ssh into it and entering the passphrase is no inconvenience.