XPost: alt.comp.os.windows-10   
   From: mariasophia@comprehension.com   
      
   Frank Slootweg wrote:   
   >  Please don't spoil his rant with facts from the real world.   
      
   Please do not describe an intelligent technical description of how to   
   properly set up a computer or phone as a "rant", Frank.   
      
   Just stop it with your incessant personal-attack childishness.   
   It's always you who throws the first punch, Frank.   
      
   But I'm not responding to your never-ending personal attacks, Frank.   
   I'm just asking you politely and publicly to cut it out.   
      
   Stick to the technical topic, Frank.   
      
   If you have nothing technical to say, Frank, then please refrain from   
   personal attacks simply because you can't address the technical issues.   
      
   You don't have to agree that people who have good privacy practices have no   
   need for silly biometric gimmicks, but you should at least attempt to   
   understand the value of encrypted containers (e.g., Veracrypt) and   
   encrypted databases (e.g., KeepassDX).   
      
   To bring this conversation back to the technical level that is useful to   
   others, I ask you to please see my "technical" response (copied below)   
   moments ago to Daniel70 where I simply ask you, Frank, to remain civil and   
   technical on this ng.   
      
   If you can't be technical Frank, then at least stop it with the incessant   
   personal attacks.   
      
   Daniel70 wrote:   
   >> As such, I haven't had a password or PIN on any device unless it   
   >> requires it, which as far as I know, only iOS requires you to have a   
   >> password to the mothership account (but you don't need to protect the   
   >> device itself).   
   >   
   > It intrigues me when I see someone who has to enter a Password on their   
   > Mobile Phone before they can use it.   
      
   Yup. What a waste of time. It's like having to enter a password (or silly   
   marketing biometric gimmicks) just to read the time display on your watch.   
      
   > WHY??   
      
   Heh heh heh... there's a reason. But it's not what most people think.   
   HINT: Why is Microsoft desperate to enforce an Apple-like mothership model?   
      
   > As long as YOU don't lose your mobile phone, WHY do you need to secure it??   
      
   Even if you do lose your phone, all the burglars get is the physical phone.   
   Your passwords & personal data (e.g., financial records) are encrypted.   
      
   All they get that is "personal data" is likely only your DCIM folder.   
   Mine would bore the burglar to death (e.g., screenshots of my devices).   
      
   > (I don't do Banking/Credit Card on my mobile phone so what would I lose   
   > if I lost it?? Photos!!)   
      
   Even if you did have financial data on your device, it's encrypted.   
      
   >> Of course, I practice good computer hygiene, so I don't have anything   
   >> on my devices that a burglar could use against me,   
   >   
   > Yeap!   
      
   I can't imagine what would be on a device that a burglar could use.   
   But I'm assuming people don't log into the mothership account.   
      
   Note: Only iOS requires that mothership account. Nobody else.   
      
   >> which means my medical and financial records are in a Veracrypt   
   >> encrypted volume while my passwords are in KeepassXC on Windows (with   
   >> compatible apps for them on Android).   
   >   
   > Too Hi-Tech for me. ;-P   
      
   Veracrypt is very easy to use on Windows to create encrypted containers.   
    https://veracrypt.io/en/Home.html   
    In practice, it's just a Windows lettered drive "e.g., the "V:" drive).   
      
   KeepassDX is also very easy to use on Windows to save your passwds.   
    https://www.keepassdx.com/   
    In practice, it's just a "text" database that happens to be encrypted.   
   --   
   On Usenet, old men with vast experience voluntarily share that knowledge.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)