• 1 Post
  • 25 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle
  • NTFS is considered pretty stable on Linux now. It should be safe to use indefinitely.

    If you’re worried about the lack of Unix-style permissions and attributes in NTFS, then getting BTRFS or ext4 on Windows may be a good choice. Note that BTRFS is much more complicated than ext4, so ext4 may have better compatibility and lower risk of corruption. I used ext3 on Windows in 2007 and it was very reliable; ext4 today is very similar to ext3 from those days.

    The absolute best compatibility would come from using a filesystem natively supported by both operating systems, developed without reverse engineering. That leaves only vfat (aka FAT32) and exfat. Both lack Unix-style permissions and attributes.











  • Yeah, it’s definitely a problem, and genetic information could end up getting linked. Even if a person thinks they might not have DNA in any existing database, whether criminal, medical, or otherwise, there’s no telling what might happen in the future. I can think of a few different ways a person might involuntarily, through no fault of theirs, get their DNA forcibly taken with no legal recourse.

    Every path here will have some tradeoffs. But the odds of getting linked are probably much lower outside your home country.



  • My best recommendation would be to go to a testing lab and provide a fake name. It should work. I’ve never been ID’d at any doctor’s office, and one time did even receive healthcare under a fake name with no trouble. Of course, that means your insurance won’t cover anything, but that’s the unfortunate reality of US healthcare. Also, they probably won’t delete your data. HIPAA includes no right to be forgotten, and in some cases, may even mandate retention for several years.

    Sorry I don’t have a better solution. I think your best bet is to distance this genetic data as much as possible from your real identity.

    Alternately, you could try going somewhere outside the US.

    I completely agree that HIPAA is dead. One time when I went to a new doctor’s office, totally unaffiliated with any doctor I’d ever seen before, the doctor instantly pulled all my medical records from several other places. They didn’t even get my verbal permission; they just did it. If that’s the level of security on these databases, and doctors are allowed to access them on old unsupported Windows computers, then it’s almost certain that the databases have tons of undetected data breaches. They’ve probably been scraped completely by multiple attackers.


  • I have three ideas: First, you could switch the desktop environment to one of the ones that has a GUI settings tool to set passwordless automatic sign in. I think Gnome 3 on Ubuntu, and Mate Desktop on Linux Mint have that feature. There are probably others.

    Second, you could switch your display manager to “nodm”. The display manager is the thing that runs the X server or Wayland, and it starts the greeter (the greeter is the program that shows the login screen). nodm is a special display manager that doesn’t use a greeter or ask for a password. It immediately starts the session using the username and desktop environment specified in its configuration file.

    I use nodm for my HTPC and it works very well. The only downside is that you have to edit its configuration file, /etc/default/nodm , using a text editor. I’m not aware of any GUI configuration tool for it. However, it’s pretty easy to configure.

    Third, you could abandon all display managers, and start the session manually, either from a shell script, or over SSH. This is a little more complex. You will probably want to get comfortable with SSH before trying this (SSH is the command-line analog of remote desktop).




  • What do you expect them to say? That they’re proud of this guy? Even though he’s clearly a madman?

    I know IRL gun nuts, and none of them would identify with this person. Also, none of them subscribe to the fallacy/straw-man of a “good guy with a gun”. The ones who carry concealed would remind you that they are carrying for themselves, not for you. If you find an active shooter in a mall, you can count on them… to run away.

    Skillful gun nuts know that shooting defensively is never worth the legal hassle unless it saves your life (or a family member’s life).

    The shooter in this article is nothing like any of the gun nuts I’ve ever met. This shooter is another Kyle Rittenhouse, someone anxious for a chance to kill a person and get away with it under the excuse of defense.


  • Limonene@lemmy.worldtoMildly Infuriating@lemmy.worldMFA
    link
    fedilink
    English
    arrow-up
    74
    arrow-down
    14
    ·
    6 months ago

    I agree with this sentiment. Steam notably falls into the third category, while otherwise being pretty good.

    But I’m quite disgusted now seeing an image of a Yubikey for the first time. I’ve heard so many good things about them that it’s a major disappointment to see now that they use that awful noncomplaint shape of USB plug.

    There are two very important reasons for the metal shield around USB plugs: 1. For ESD protection, and 2. to hold the receptacle’s tongue in place and prevent it from bending away and losing contact. Every USB device I’ve owned that was a flat plug (like this Yubikey image in this post) has within a month deformed the USB receptacle it’s plugged into to the point that the device no longer works in that port. Compliant USB devices still work in that port’s deformed receptacle, because they have a correct metal shield that bends the tongue back into the correct position.


  • The good news is: the error shown there was a PCIe bus error, which means the error is somewhere between the NVME controller and your processor’s PCIe interface. Also good news: the errors you experienced were fully corrected, so you probably lost no data.

    So the flash memory in the drive isn’t failing. That’s good because if the flash memory starts failing, it’s probably only going to fail more. In this case, your errors may be correctable: by replacing the motherboard, by replacing the processor, by reseating the NVME drive in its slot, by verifying that your power supply is reliable…

    However, if your NVME controller actually does fail, it will be little consolation to tell you that your data is all still there on the flash chips, but with no way to get it. So now might be a good time to make a backup. Any time is a good time to make a backup, but now is an especially good time.

    If you keep getting these errors at the same rate, then you probably don’t need to do anything, since the errors are being corrected. If you’re worried, you could use BTRFS and enable checksumming of data.


  • Using a VPN (like Tailscale or Netbird) will make setup very easy, but probably a bit slower, because they probably connect through the VPN service’s infrastructure.

    My recommended approach would be to use a directly connected VPN, like OpenVPN, that just has two nodes on it – your VPS, and your home server. This will bypass the potentially slow infrastructure of a commercial VPN service. Then, use iptables rules to have the VPS forward the relevant connections (TCP port 80/443 for the web apps, TCP/UDP port 25565 for Minecraft, etc.) to the home server’s OpenVPN IP address.

    My second recommended approach would be to use a program like openbsd-inetd on your VPS to forward all relevant connections to your real IP address. Then, open those ports on your home connection, but only for the VPS’s IP address. If some random person tries to portscan you, they will see closed ports.


  • You know that stuff that appears on the screen before the operating system? That is the computer’s firmware. Sometimes it shows a brief memory check, sometimes it has a silly error message like “No keyboard detected. Press F1 to continue.” Sometimes it’s just a big image of the motherboard’s manufacturer’s logo. That firmware exists independently of the operating system, and will run even if you don’t have any operating system installed.

    Most people refer to the firmware as the “BIOS”, but technically, BIOS refers to an API between the firmware and the operating system. About a decade ago, some people decided that “BIOS” was going to be replaced by “UEFI”, and operating systems would start having a new way to boot. What ended up happening is: the firmware on all recent computers supports both UEFI and BIOS interfaces (and everyone still calls it “BIOS”). Recent Windows versions seem to only boot in UEFI mode, but most Linux distros can boot in either UEFI or BIOS mode. The GRUB bootloader can also start itself up in either UEFI or BIOS mode.

    USB live operating systems are limited in size and may have less functionality than other operating systems, so maybe they are only able to boot in one method or another. Try looking around in the firmware (or “BIOS” if you prefer) to see if you can change the boot method to allow both UEFI and BIOS operating systems.

    It may help if you can take a picture of some of the firmware’s boot configuration menus.