Comments by "MyTech" (@mytech6779) on "Severe (9.9 / 10) Linux Vulnerability Announced, Details Kept Secret" video.

  1. ​ @Turalcar  Hanlon's razor is a flawed concept as typically applied, because it looks at the bulk of actors without considering their interactions and the differential of influence between them. 9/10 may be incompetent but they are being used by the 1/10, this does not mean a problem has a 90% chance of being caused by incompetence. Quite the contrary, the incompetence is acting as mechanical advantage for the malicious intent that is really doing the driving. However, the apparent actor being incompetent rather than malicious would be greater than 90%, because the one manipulating knows enough to remain obsured.
    7
  2. Dumps all its drive content to a public FTP server with your address as the directory name then combusts.
    4
  3. Rubberhose attacks don't work to reverse the effect of reasonably implemented deadman switches and panic buttons.
    3
  4.  @MrHerbalite  For sure many don't seem to understand that high level tools are just assemblies of low level components and magic pixie dust is not one of those components.
    2
  5. There is systemd on BSD.
    2
  6.  @dkosmari  More macros!!
    1
  7.  @qbasic16  BINGO!!!:face-blue-smiling:
    1
  8. "the" browser ?
    1
  9. ​ @jttech44  I used them all the time when I operated certain types of heavy machinery and seen them do the job as intended. They work quite well actually. Also, timer based vaults exist for good reason. All a computer system needs is to use full drive encryption and a script to delete the master keys either activated by panic button or on a timer that needs to be regularly refreshed (or the old 3 strikes your out password trigger). Generally the user password is not the full key, it is only used to access and suppliment the master keys, you need both halves to get anything. Taking some care to select drives that will reliably imediately overwrite old data and using synchronous write commands in the software (So writes don't sit in the cache.) avoiding copy on write hardware and filesystems (eg SSD wear leveling). There are some more sophisticated approaches, but this is just a YT comment.
    1