From: elronnd@elronnd.net   
      
   On Thu, 17 Jun 2021, muta...@gmail.com wrote:   
   > TLS 1.0 means that the "glorified telephone people" need to go to some   
   > effort to see my passwords, and may lose their jobs if they are caught.   
   > Sounds good to me.   
      
   > The browser people seem to be in a conspiracy to prevent people from   
   > accessing a TLS 1.0 server, even internally within a company.   
      
   There are very sound reasons to disallow the use of TLS 1.0 entirely.   
   Namely: downgrade attacks.  There is no conspiracy.   
      
   (That being said, I'm not sure what browser vendors were smoking when   
     they decided that a self-signed certificate is cause for a   
     !sensationalistic! warning, but an unencrypted connection is not.)   
      
      
   > Sounds to me like there's a market for a rival browser that enables the   
   > use of TLS 1.0, perhaps with a warning.   
      
   Not really.  You can (relatively) trivially compile old versions of   
   chrome/firefox.   
      
      
   > I assume there is no public domain code available to do [TLS]   
      
   https://github.com/eduardsui/tlse   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)