Giver of skulls

Verified icon

  • 0 Posts
  • 11 Comments
Joined 101 years ago
cake
Cake day: June 6th, 1923

help-circle

  • Administrator is not root. NT AUTHORIRY\System probably comes closest. You rarely need to interact with that account because Window’s security system doesn’t have the same mix of authentication systems most Linux systems have (users + container APIs + PolKit).

    Windows also supports mixed case filesystems just fine. It’s not the default, so your programs will probably screw up, but it’s just a flag. You can also mount filesystems like ext4 and btrfs on Windows (though booting from them doesn’t really work).

    Also, Windows runs Libreoffice and GIMP just fine. You don’t need to, because you have better sofware available (pirated or paid).

    As for security, Windows is MUCH better unless you’re a cybersecurity specialist with too much time in their hands. Most major distros don’t even come with a firewall enabled by default, let alone a firewall for outgoing traffic. And the best AV I’ve seen for Linux is Microsoft’s enterprise version of Windows defender. In terms of hacking tools, they’re mostly written in languages Python, most of them work on either platform.

    For development, Linux has a slight edge, but with WSL2 it really doesn’t matter much.


  • Running Linux on computers with Nvidia hardware proves that Linux and Windows both have their problems dealing with device drivers. Linux’ benefit is that is has higher standards because the kernel devs need to sign off on driver, but that has downsides of turning away potential driver developers (as getting your code into Linux is a quite a complex thing just on its own). Linux also doesn’t have many drivers in general it seems, unless your device has some kind of generic fallback that disables any special features.

    My kernel panics generally don’t display anything, the display just freezes and I need to force reboot the computer.





  • Then, what prevents whosoever, to copy that file through cloning the complete disk?

    Nothing. At most, you can have a hardware encrypted drive that won’t permit access to the encrypted data without a password, but the file will remain available after unlocking that. Plus, dedicated people (law enforcement, data recovery specialists) may be able to get access to the flash chip itself unless you buy one that self destruct on any tampering attempts (and even those have flaws).

    You cannot prevent copying of data if that data is readable at disk level. At most, you can make the data useless by padding a layer of encryption (as well-encrypted data may as well be random data without the key material). That’s why everyone is going for encryption: encrypted files may as well be inaccessible to anyone who doesn’t know the passphrase. There’s no sense in copying a file which you cannot possibly read any bytes from.

    If the key is gone (i.e. the real key is a password protected file that gets overwritten so even the password doesn’t work anymore), the file becomes irretrievable. This is sometimes called “cryptographic erase” in the context of disks. There are variations of this, for instance, storing the key in the computer’s processor (fTPM) behind a password, and clearing that key out. There’s no way to get the key out of the fTPM so it cannot be backed up. Even if someone were to guess your password, the file will forever remain locked. Or at least until someone manages to break all cryptography, but even quantum computers don’t know how to do that part yet.

    If you’re willing to go deep, you could reprogram the firmware on your SSD/HDD to refuse reading the file. A few years back, someone made a proof of concept firmware that detected disk imaging attempts (because all blocks on the disk were read in order) and had the firmware return garbage while secretly wiping the disk when this detection triggered. You could, in theory, write firmware that refuses to read that block of data. However, if whoever you’re hiding this file from know about that, they can take out the platter/memory chips and dump them directly, bypassing your firmware entirely.


  • “undoing the protection should include filling in a password” That sounds like an encrypted drive. There are USB keys that’ll require software to enter an encryption password before you can do anything (including deleting the contents).

    If you’re on Windows, try Bitlocker or Veracrypt. You can create hard disk images that can be mounted temporarily with a password.

    Same can also be done on other operating systems, though I don’t know what tools yours come with.

    In a pinch, you can just create a password protected 7zip archive, though viewing and editing those files usually involves a temporary copy.

    There’s no way to prevent a file that’s loaded in memory from making it back to the disk. The best you can do is also encrypt the system drive so only people who know the encryption password can boot the computer that’s accessing these files.