pgo_lemmy

If the main site gets compromised the credentials there must be considered lost and known to che attackers.

with a pull backup that's not an issue because the main site has no access to the remote system; it is a process on the remote site that has credentials to access the main site and not the other way around.

the remote system may ~~receive~~ retrieve a compromised copy of the data, but the attacker cannot tamper with previous backups so recovery is still possible.

Fifa Agent Platform -> FAP

pun intended?

Furry equipment FTW

https://fursonafy.com/fursuit-cooling-vests-everything-you-need-to-know/

last thing missing in your post is a complaint for slow migration on a 1gbit link...

you can complain as much as you want because proxmox is not vmware or you can embrace proxmox and make the effort to move/update/refresh your knowlwdge on to the new environment.

sarebbe bello se oltre a prevedere e mitigare/intercettare il comportamento stupido dell'utente (stupido?) con la soluzione tecnica si puntasse anche alla formazione.

ma la soluzione tecnica costa meno, richiede meno risorse, fa fare bella figura più alla svelta.

magari in questo caso faranno entrambi.

ecco cosa succede quando chi fa le regole non ha idea di cosa sta regolando...

dato che il problema sono le persone che si fanno fregare, cambiare strumento non risolve il problema.

così come gli utenti cliccavano a caso facendosi fregare gli account signal, così si faranno fregare gli account della nuova app governativa.

This is the way. 🤭

The second install should be easier since is done just after a test one.

Add a second node using the new drive, move all vm to the new node, decommission old node, rebuild the old node with the new drive.

You can get away with a disk clone but in my opinion a vm move is the proper way to go.

Adding a new node you start with a clean install, any quirk you have on the old hw will be finally washed away (or will bite you back and be properly documented), you have a quick way back should anything go sideways (the clone too provides a quick way back, but i like this way much more ^^), you get some hands on multi node experience that will be useful for ha setup.

Normal background noise. ssh is a well known protocol/port and scanning is automated.

my home router is the stock one from my isp and have no vpn capabilities.

I put a port forward on the router and then configured everything on the internal node; in my case it is an opnsense vm running on proxmox.

I wouch for the VPN route... VPN servers are built to be exposed, are hardened/engineered to resist the harshness of the net and are somewhat safe even with default settings.

Should you publish on the wild a few web apps, you would have to harden, monitor and manage a bunch of environments and/or frameworks with a load of quirks each.

A VPN is easier to maintain and safer for your data with a lower effort.

The article is on a 'pay or ok' site.