registry team mailing list archive

Thread
Date

[Bug 627973] Re: Assertion failed at socket.c:629

To: registry@xxxxxxxxxxxxxxxxxxx
From: Jarrett Miller <627973@xxxxxxxxxxxxxxxxxx>
Date: Mon, 27 Sep 2010 11:43:49 -0000
Reply-to: Bug 627973 <627973@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

I tested the AMD64 build on Lucid today. It fixes the socket assertion
failure but still features a regression relative to upstream.

With the build from you PPA and the config file I provided I get the following in syslog:
TLS: Initial packet from [AF_INET]192.5.38.152:49308, sid=713f6ed1 b48b32c4
Authenticate/Decrypt packet error: packet HMAC authentication failed
TLS Error: incoming packet authentication failed from [AF_INET]192.5.38.152:49308
Fatal TLS error (check_tls_errors_co), restarting
OpenVPN started by inetd/xinetd cannot restart... Exiting.

-----------------------------------------------------------------
To fix it I had to comment out the "tls-auth" lines in my client and server configuration files.
For example I commented this out in my server configuration file:
# tls-auth /etc/openvpn/ta.key 0 # This file is secret

After doing that it works like upstream, except I am not getting the PSK
protection of the TLS negotiation. So its still not working right but at
least it no longer produces the socket assertion message.

-- 
Assertion failed at socket.c:629
https://bugs.launchpad.net/bugs/627973
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.