Some middle-aged guy on the Internet. Seen a lot of it, occasionally regurgitating it, trying to be amusing and informative.

Lurked Digg until v4. Commented on Reddit (same username) until it went full Musk.

Was on kbin.social (dying/dead) and kbin.run (mysteriously vanished). Now here on fedia.io.

Really hoping he hasn’t brought the jinx with him.

Other Adjectives: Neurodivergent; Nerd; Broken; British; Ally; Leftish

  • 2 Posts
  • 2.76K Comments
Joined 2 years ago
cake
Cake day: August 13th, 2024

help-circle











  • What I’ve read just now is what I’d deliberately not gone looking for up to this point in case I found this out.

    Linux and Windows happen to require that the executables that access that information be run with root privileges, but it looks like that’s merely an affectation.

    It seems that any old piece of software, without root or other privileges, can independently run the CPUID instruction that obtains a processor’s serial number.

    I do not like this one bit.




  • I would be very interested to know how they are able to identify a specific CPU. The article speculates but does not answer this question.

    The fact that this is even possible is a security nightmare.


    OK, I’ve done a bit more digging and pieced it together. Acknowledgement to @dual_sport_dork@lemmy.world for prompting me to try (again) to find a command that might do it among other things.

    IMO, this sort of information shouldn’t be in processors in the first place, but apparently it is there and needs admin/root access to, well, access it.

    … and the game in question requires kernel-level anti-cheat, so of course, it has the necessary access.

    The command for Linux is sudo dmidecode -t processor, which dumps a lot of info including an ID field, which is supposedly the CPU’s specific identifier. It can be grepped for or otherwise filtered out.

    My own Ryzen gives 8 hexadecimal pairs, so it’s a 64-bit value.

    I would not know that that was unique to my specific individual processor if I had not been told, but I’ll assume that at least part of it is not unique between Ryzens of the same calibre. (I won’t be posting any of it for comparison, for obvious reasons.)

    So the upshot is, if you don’t want to be identified right down to your CPU, don’t run programs as root if there’s any chance of them phoning home.


  • I once took down a production server with a script that was an unintentional resource thief. The “oh sh-t” was watching the script grind to a halt… and then the phone started ringing.

    Borderline on the non-destructive there because the server recovered fine after a reboot and nothing was lost except uptime. Sometimes a server would choke anyway, and the company assumed it was that, but that time it was my fault.

    I had to answer more than the one call regarding that, feeling sick to my stomach, so I didn’t escape unpunished.




  • Oh hey, I own an old Star Trek annual that has this story in it. Basically the planet has spores in the atmosphere that turn people into giant carnivorous plants. A couple of redshirts are irrevocably altered and can’t be saved, but plot armour saves the main players as usual.

    They may have used the idea for real in the TNG episode where Geordi begins to turn into an alien species after several people he was working with have already done the same.

    The same annual has a story in it about a race of humanoids who turn their lives over to machines. They become clueless, waited on hand and foot while it runs amok turning their planet into an empty concrete wasteland full of buildings no-one will ever live in.

    Basically predicted the warning signs of AI 60 years ago.