Did you have atime on?

What I have now is one VM that has the array volume passed through and the VM exports certain folders for various purposes to other VMs. So for example, my application server VM has read access to the music folder so I can run Emby. Similar thing for photos and shares out to my other PCs etc. This way I can centrally manage permissions, users etc from that one file server VM. I don’t fancy managing all that in Proxmox itself. So maybe I just create the zpool in Proxmox, pass that through to the file server VM and keep the management centralised there.

I’m not intending to run Proxmox on it. I have that running on an SSD, or maybe it’s an NVME, I forget. This will just be for data storage mainly of photos that one VM will manage and NFS share out to other machines.

Q

Quake Quake II

But maybe U

Unreal Tournament 2004

It’s nothing to do with static assignment of a prefix from my ISP, I have that. It’s to do with static assignment of IP addresses within my own house! Use DHCP and android will not use it; use SLAAC and I have no control over IP addresses and therefore cannot set up sensible firewall rules per device.

Probably helps add a certain gravitas.

Snaps themselves are a GPLd format

To be fair, that evidence is the most proof like I’ve ever seen. Incredible.

XML is a superior format to Json or yaml or any of those other trendy formats around today. It’s the hill I’m willing to die on because I’m right.

You were saying the input size doesn’t matter because you only store the hash which is always the same size. What I’m saying is that the input size really does matter.

You absolutely should set upper limits on all input fields because it will be abused if you don’t. Systems should validate their inputs, passwords included

deleted by creator

You can make a client hash it, but if you don’t reject large inputs to your API a client can send enough data to DOS you anyway.

The resulting hash will always be the same size, but you don’t want to have an unlimited upper bound otherwise I’m using a 25GB blueray rip as my password and your service is going to have to calculate the hash of that whenever I login.

Sensible upper bounds are a must to provide a reliable service not open to DDOS exploits.

Not necessarily. Presumably the change password form requires entering the old and new password at the same time. Then they can compare the two as plain text and hash the old password to make sure it matches, then if so, hash the new password and overwrite it. Passwords stored hashed, comparison only during the change process. A theme on this is checking password complexity rules during the login process and advising to update to something more secure. It’s possible because you’re sending the password as plain text (hopefully over a secure connection), so it can be analysed before computing the hash. This even works if the hash is salt and peppered.

Hidden and Dangerous

Only H&D2 is on steam

The original was fantastic and v2 built on that. Fantastic 3rd person WW2 tactical shooter. Haven’t seen anything like it in over 20 years since.

Been running Ubuntu LTS releases on all my server VMs for 8 years and haven’t had a single problem. Absolutely solid as a rock. Fantastic support, loads of guides to do anything. Plus you can get 10years of support as a home user with a free Ubuntu Pro subscription.

I’d honestly just go Ubuntu server LTS and learn to configure it through the terminal. It’s not too difficult to setup. NFS and Samba shares.

If more than 0.1% of people do that I’d be flabbergasted

Use a better search engine.

Those of you who “can’t live without google”, need to get a grip.

“Leaked”.

All leaks are deliberately orchestrated to fan the hype train.