From: irfon@ambienautica.com   
      
   On Sunday, May 8, 2022 at 11:12:55 PM UTC-4, Irfon-Kim Ahmad wrote:   
   > On Saturday, May 7, 2022 at 11:20:40 PM UTC-4, drago marelic wrote:    
   > > IA> PuTTY on Windows, and ssh from the local command line of the system    
   > >    
   > > when you do it from the command line try putting -c 3des-cbc at the end    
   > > it might be a cryptography problem   
   > When I try that, instead of hanging until I ^C it, it closes the connection   
   immediately. So... different behaviour depending on protocol? Not sure if   
   that's a step forward or not. :)   
      
   Okay, I solved this. Documenting for anyone else who has this issue:   
      
   cryptlib 3.4.6 didn't work for me, but did generate a faulty ssl.cert file in   
   "data". Trying any other version would thereafter fail (earlier versions   
   wouldn't even load and listen, but 3.4.5 would fail because of the bat cert).   
   Shutting down mis,    
   removing the cert file, replacing cryptlib with 3.4.5, starting it back up,   
   trying a connection to let it generate a new cert file, and then reconnecting   
   did the trick.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)