XPost: alt.comp.os.windows-10   
   From: user@example.net   
      
   On 01/04/2024 22.39, Newyana2 wrote:   
   > "J.O. Aho"  wrote   
   >   
   > | There is less risk of using the compromised xz tarball than using your   
   > | current ms-windows   
   >   
   >    You're getting more glib and adversarial with each post.   
   > The risks with Windows depend on a lot of things. As does   
   > the risk with anything. Computers are not hacked by pixies.   
      
   Then I guess you missed the windows metafile image code execution   
   (MICE), so you could say you get hacked by a pixel, no matter if it's   
   your mail client, your browser of a image you got from a friend on an   
   usb stick that you take a look in windows picture.   
      
      
   > They're hacked by people exploiting network communication   
   > methods that are inherently unsafe.   
      
   You know your browser and your mail client are your weakest points, no   
   matter if the communication is encrypted or not.   
      
      
   >     If you don't want to deal with that directly then the best   
   > you can do is to allow the dripfeed updates, run anti-virus,   
   > minimize valuable data that you allow on your computer,   
   > like credit card numbers, and hope that some update doesn't   
   > break your system.   
      
   I understand that you are reluctant to update for you are afraid that   
   things will break, that caused by the bad QA checking done by a specific   
   company, but instead of using something better you keep on hanging   
   around with a old install that hasn't been updated as it's EOL, harming   
   the rest of us with your vulnerabilities. Have you fixed CVE-2008-5424   
   and CVE-2010-3147 yet?   
      
      
   > If you're actually going to deal with   
   > security it's more complicated.   
      
   Yes, it is complicated and you need to be able to analyze the source   
   code of all programs you run, even the BIOS and OS, if you running a   
   somewhat modern CPU you would need the access to the source code of the   
   minix that is running on the CPU. Don't forget the same thing applies to   
   your other devices like firewall. Don't forget that you should compile   
   everything from the source you have analyzed and deemed as safe, each   
   time there is a security patch you should analyze it and decide if   
   applying it to your code and then recompile the application and all that   
   depends on it in a static manner.   
      
   It's a quite a lot of work and not all have the skill to do so and then   
   there is the problem that you don't have access to all the source code,   
   so you have to trust on others judgment and as they also are humans,   
   they too can make mistakes and that's why all code has bugs.   
      
   --   
     //Aho   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)