I tried applying the patch from message #16 at http://code.google.com/p/openvpn-auth-ldap/issues/detail?id=31 and then changing the runtime from 'GNU' to 'modern' (after running autoconf to update configure), and also adding libgnustep-base-dev as a Build-Dep.
The result is that it doesn't segfault, but instead has an unhandled exception. lennartsorensen:/tmp/openvpn-auth-ldap-2.0.3# openvpn --dev null --plugin /usr/lib/openvpn/openvpn-auth-ldap.so Wed Apr 17 15:43:20 2013 OpenVPN 2.3_rc1 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [eurephia] [MH] [IPv6] built on Apr 17 2013 Wed Apr 17 15:43:20 2013 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables 2013-04-17 15:43:20.949 openvpn[27355] autorelease called without pool for object (0x7f5dfd20eea0) of class NSMethodSignature in thread <NSThread: 0x7f5dfd1b7ae0> 2013-04-17 15:43:20.959 openvpn[27355] autorelease called without pool for object (0x7f5dfd27f730) of class NSMutableDataMalloc in thread <NSThread: 0x7f5dfd1b7ae0> 2013-04-17 15:43:20.959 openvpn[27355] autorelease called without pool for object (0x7f5dfd20ffc0) of class GSCodeBuffer in thread <NSThread: 0x7f5dfd1b7ae0> 2013-04-17 15:43:20.959 openvpn[27355] autorelease called without pool for object (0x7f5dfd27b5c0) of class GSCInlineString in thread <NSThread: 0x7f5dfd1b7ae0> 2013-04-17 15:43:20.959 openvpn[27355] autorelease called without pool for object (0x7f5dfd27d710) of class NSException in thread <NSThread: 0x7f5dfd1b7ae0> 2013-04-17 15:43:20.960 openvpn[27355] autorelease called without pool for object (0x7f5dfd1755b0) of class NSLongLongNumber in thread <NSThread: 0x7f5dfd1b7ae0> 2013-04-17 15:43:20.960 openvpn[27355] autorelease called without pool for object (0x7f5dfd27d940) of class NSLongLongNumber in thread <NSThread: 0x7f5dfd1b7ae0> 2013-04-17 15:43:20.960 openvpn[27355] autorelease called without pool for object (0x7f5dfd2723a0) of class NSLongLongNumber in thread <NSThread: 0x7f5dfd1b7ae0> 2013-04-17 15:43:20.960 openvpn[27355] autorelease called without pool for object (0x7f5dfd255410) of class NSLongLongNumber in thread <NSThread: 0x7f5dfd1b7ae0> 2013-04-17 15:43:20.960 openvpn[27355] autorelease called without pool for object (0x7f5dfd253980) of class NSLongLongNumber in thread <NSThread: 0x7f5dfd1b7ae0> 2013-04-17 15:43:20.960 openvpn[27355] autorelease called without pool for object (0x7f5dfd246780) of class NSLongLongNumber in thread <NSThread: 0x7f5dfd1b7ae0> 2013-04-17 15:43:20.960 openvpn[27355] autorelease called without pool for object (0x7f5dfd1a7060) of class NSLongLongNumber in thread <NSThread: 0x7f5dfd1b7ae0> 2013-04-17 15:43:20.960 openvpn[27355] autorelease called without pool for object (0x7f5dfd1a6550) of class NSLongLongNumber in thread <NSThread: 0x7f5dfd1b7ae0> 2013-04-17 15:43:20.960 openvpn[27355] autorelease called without pool for object (0x7f5dfd1bb7d0) of class NSLongLongNumber in thread <NSThread: 0x7f5dfd1b7ae0> 2013-04-17 15:43:20.960 openvpn[27355] autorelease called without pool for object (0x7f5dfd235930) of class NSLongLongNumber in thread <NSThread: 0x7f5dfd1b7ae0> 2013-04-17 15:43:20.960 openvpn[27355] autorelease called without pool for object (0x7f5dfd27b770) of class NSLongLongNumber in thread <NSThread: 0x7f5dfd1b7ae0> 2013-04-17 15:43:20.960 openvpn[27355] autorelease called without pool for object (0x7f5dfd237e70) of class NSLongLongNumber in thread <NSThread: 0x7f5dfd1b7ae0> 2013-04-17 15:43:20.960 openvpn[27355] autorelease called without pool for object (0x7f5dfd257a20) of class NSLongLongNumber in thread <NSThread: 0x7f5dfd1b7ae0> 2013-04-17 15:43:20.960 openvpn[27355] autorelease called without pool for object (0x7f5dfd270390) of class NSLongLongNumber in thread <NSThread: 0x7f5dfd1b7ae0> openvpn: Uncaught exception NSInvalidArgumentException, reason: GSFFIInvocation: Class 'LFAuthLDAPConfig'(class) does not respond to forwardInvocation: for 'alloc' I guess it's an improvement, but not a solution. Somehow this doesn't look rescuable. Perhaps if upstream had a new release sometime in the last 5 years it might be in a better state, but as it is, it seems to simply not be compatible with gobjc 4.7+. Now if the exception is because I don't have a valid config, then perhaps it is progress. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
