tis 29 apr. 2025 kl. 10:00 skrev Michael Osipov <micha...@apache.org>:
> On 2025/04/27 13:00:53 Graham Leggett via dev wrote: > > Hi all, > > > > When attempting a routine svn update from svn 1.14.3 on MacOS (via > macports), I'm getting the following sudden failure: > > > > Little-Net-8818:xxx minfrin$ svn update > > Updating '.': > > svn: E170013: Unable to connect to a repository at URL ' > https://xxx/trunk' > > svn: E120171: Error running context: An error occurred during SSL > communication > > > > What mechanism exists to get the error that occurred during SSL > communication? > > > > Google is full of people trying things at random, so isn't of any help. > tcpdump shows the client hello, the server hello, the server key exchange > etc, then the client side puts the phone down with no graceful TLS shutdown. > > > > Is there a mechanism to coax an error out of the client side, or is this > something I will have to patch? > > Wireshark, tcpdump. Can you check which version of Serf and OpenSSL you are using? Could it be that your server is using a newer certificate suite that isn’t supported by your version of OpenSSL? Kind regards Daniel
