Likely you needed to include the intermediate cert chain. Let’s encrypt sets that up automatically so it’s quite a bit easier to get right.
Likely you needed to include the intermediate cert chain. Let’s encrypt sets that up automatically so it’s quite a bit easier to get right.
Your experience may depend on which distro you use and how you install things. If you use a distro with a stable upgrade path such as Debian and stick to system packages there should be almost no issues with upgrades. If you use external installers or install from source you may experience issues depending on how the installer works.
For anything complex these days I’d recommend going with containers that way the application and the OS can be upgraded independently. It also makes producing a working copy of your production system for testing a trivial task.
I’n Windows it is not stored in a keyring but instead in the registry. This has basically the same security threat model as a local key file.
The ssh-agent on Linux will do what you want with effectively the same security. The biggest difference being that it doesn’t run as a system service but instead runs in userspace which can make it easier to dump memory. There are some other agent services out there with additional security options but they don’t change the threat model much.
My memory of the cp command is that attributes such as file times were transferred at the last step. I think this would make rsync safe in most situations where a system crash wasn’t involved.
I think I remember running into that as well but for whatever reason I couldn’t get accelerated-x working with the opengl libraries I was using for school. Likely the issue was just a lack of understanding on my part as I don’t think I had a good grasp of the Linux library loader until well after I graduated.
I’ve had a system in the late 90s with a 3dfx voodoo card. Also had a laptop with a SIS card from the early 2000 era.
The voodoo card was THE card to have it it’s day (mine was an older second hand system though). The SIS card… for some reason they decided that standard VESA mode probing wasn’t a thing they supported and would hardware crash when that API was used. I eventually got it working in Linux after patching xfree86 to not attempt probing when loading the VESA driver.
QEMU supports either spice, vnc or sdl graphics output. If you want to copy/paste you need to use spice and install the spice agent on the VM.
My steam deck also unlinks family libraries with almost every os update. It might be an issue of overzealous hardware validation but it could also just be a bug.
It’s very likely that your disk is failing.
dd if=/path/to/file.mkv of=/new/file/path.mkv conv=noerror,sync bs=4k
Should give you a file with just the damaged bits missing.
PTSD from the days long ago when X11 error log would fill up the disk when certain applications were used.
Are they on a local disk? Thunar doesn’t render any thumbnails for remote storage by default.
They fail because you can’t trust a machine that an adversary has in their physical possession.
Software running on an untrusted computer can have code and memory injected or modified without modifying the executable files. Binary executable files are by necessity readable and someone with enough time can parse through them to fully deobfuscate and figure out what they are doing. Anti-anti-cheat systems basically perform the same code as the anti-cheat but slightly modify the result to hide the cheating. This can be done either by code swapping in the anti-cheat or at a higher level. If the anti-cheat system is looking at which processes are running then have the system feed it the real list of processes with the cheat processes removed… etc.
Trusted computing requires hardware level monitoring, validated certificates, and zero vulnerabilities since the time the certificate was provisioned. In addition, current technology would also require those base certificates to be regularly rotated and device decertified if it didn’t rotate in time to prevent physical offline hardware attacks on the certificate data. Even game consoles don’t have this level of platform trust and are often physically modified to enable cheating/piracy.
The only successful way to prevent most cheating is to run the simulation entirely server-side and then only send data to each client according to what they should know. Even then you won’t be able to prevent assisted cheating like aim-bots or texture replacements.
When rsync copying the active root I like to bind mount / to /mnt/root_fs first. This avoids the issue with needing to exclude folders with sub-mounts and will expose files to copy that might be hidden by the mounts.
It can still have issues with potential attacks that would redirect your client to a system outside of the VPN. It would prevent MitM but not complete replacement.