; 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 mech
On 2025/04/29 08:29:59 Andreas Stieger wrote:
>
> On 2025-04-29 10:00, Michael Osipov wrote:
> > On 2025/04/27 13:00:53 Graham Leggett via dev wrote:
> >
> > What mechanism exists to get the error that occurred during SSL
> > communication?
> >
> > [...]
> > Is there a mechanism to coax an error
On 2025-04-29 10:00, Michael Osipov wrote:
On 2025/04/27 13:00:53 Graham Leggett via dev wrote:
What mechanism exists to get the error that occurred during SSL communication?
[...]
Is there a mechanism to coax an error out of the client side, or is this
something I will have to patch?
Wiresh
t; 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
71: 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 excha
5 matches
Mail list logo
