1,184 karma · joined December 29, 2018
zfs-dkms + "linux-lts" (longterm kernel) seems to work better than zfs-dkms + linux (stable kernel) if you're intending to do frequent system updates - I've been running this on several machines for years with no issues.
Things like AMD SEV/SEV-ES are designed to mitigate that aspect, the implementation of which can be proven to end-users of the VM by remote attestation.
find -type f -name '*.jp2' | parallel --xargs --max-args=1 convert {} {.}.jpgSecond thought, is it fashionable now to not include a "Cancel" button in settings dialogs?
Many times, I have navigated all of the pages of a settings dialog to change a setting or multiple settings, then realise I liked it better how it was before, and have no idea what the settings were before I changed them.
Just yesterday I wanted to try a new theme in Xfce - change the theme, not happy with it, and no idea out of the 50 themes what it was before I changed it, so now I have to go through every option to find the one that was (approximately?) what it was before.
dd bs=440 count=1 if=/usr/lib/syslinux/bios/mbr.bin of=/dev/sda
Even in the age of EFI/GPT, that still gets used often (usually VM providers that only offer MBR boot).For example, user@example.com signs-in to your site and stores data they expect to be private, they stop using the mail provider and the mail provider deletes the user's account which allows it to be re-used, then another unrelated user signs-in to the site and takes-over the account.
I imagine the only viable way would be a whitelist of domains of mail providers that are known to not recycle email addresses (like Gmail), or to also check if the WHOIS data for a domain changed.
An application/site can optionally request the "email" scope during OpenID Connect sign-in, but if it is not requested (only the "openid" scope instead) then the provider must not return an email address in the ID token, or an OAuth access token which is authorized for an API method which returns the user's email address (OpenID Connect Core 1.0 section 5.4 - "Requesting Claims using Scope Values").
Google implement this (https://developers.google.com/identity/protocols/oauth2/open...), by returning only a unique numeric user ID in the returned id_token. I haven't checked other OpenID Connect providers.
vfs objects = shadow_copy2
shadow:snapdir = /home/.zfs/snapshot/
shadow:basedir = /home
shadow:sort = desc
shadow:format = auto:%Y-%m-%dT%H_%M_%SZ