• 0 Posts
  • 263 Comments
Joined 1 year ago
Cake day: April 13th, 2024
  • Kazumara@discuss.tchncs.detoTechnology@lemmy.world•Trump social media site brought down by Iran hackersEnglish
    92·
    11 days ago

    I’d start with the following, and refine if necessary:

    “Gaining unauthorized access to a protected computer resource by technical means.”

    • Port scanning --> Not hacking because there isn’t any access to resources gained*
    • Using default passwords that weren’t changed --> Not hacking because the resource wasn’t protected*
    • Sending spam --> Not hacking because there isn’t any access to resources gained
    • Beating the admin with a wrench until he tells you the key --> Not hacking because it’s not by technical means.
    • Accessing teacher SSN’s published on the state website in the HTML --> Not hacking because the resource wasn’t protected, and on the contrary was actively published**
    • Distributed denial of service attack --> Not hacking because there isn’t any access to resources gained

    * Those first two actually happened in 2001 here in Switzerland when the WEF visitors list was on a database server with default password, they had to let a guy (David S.) go free
    ** The governor and his idiot troupe eventually stopped their grandstanding and didn’t file charges against Josh Renaud of the St. Louis Post-Dispatch reporter, luckily

  • Kazumara@discuss.tchncs.detoProgrammer Humor@programming.dev•Ramsay's kitchen nightmares, but for software development
    9·
    22 days ago

    This week I heard from a network group lead of a university hospital, that they have a similar issue. Some medical devices that come with control computers can’t be upgraded, because they were only certified for medical use with the specific software they came with.

    They just isolate those devices as much as possible on the network, not much else to do, when there is no official support and recertification for upgrading. And of course nobody wants to spend half a million on a new imaging device when the old one is still fine except for the OS of the control computer.

    Sounds like a shitty place to be, I pity those guys.

    That said, if you were talking about normal client computers then it’s inexcusable.

  • Kazumara@discuss.tchncs.detolinuxmemes@lemmy.world•windows update
    5·
    1 month ago

    Pre-UEFI they were fighting over the boot sector, sure, but now that everything is more well defined, and every OS can read the FAT32 ESP? Never seen it…

    At worst the UEFI boot entry is replaced. There are some really shitty UEFI implementations out there which only want to load \efi\microsoft\boot\bootx64.efi or \efi\boot\bootx64.efi, or keep resetting you back to those.

    Assuming you were dumped into Windows suddenly, you can check if you have the necessary boot entries still with bcdedit and its firmware option

    bcdedit /enum firmware

    If you just have a broken order you can fix it with

    bcdedit /set {fwbootmgr} displayorder {<GUID>} /addfirst

    If you actually need a new entry for Linux it’s a bit more annyoing, you need to copy one of the windows entries, and then modify it.

    bcdedit /copy {<GUID1>} /d "Fedora"
bcdedit /set {<GUID2>} path \EFI\FEDORA\SHIM.EFI
bcdedit /set {fwbootmgr} displayorder {<GUID2>} /addfirst

    Where GUID1 is a suitable entry from windows, and GUID2 is the one you get back from the copy command as the identifier of the new entry. Of course you will have to adjust the description and the path according to your distro and where it puts its shim, or the grub efi, depending on which you’d like to start.

    Edit: Using DiskGenius might be a little more comfortable.