Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement

2012-06-14 Thread Ralf Jung
Hi, > I'm not entirely sure when plasma-widget-networkmanagement registers its > NM VPN agent. This is almost certainly a problem with that, rather than > the openconnect-specific parts. Can you restart kded perhaps? I logged out and in, so everything was restarted. Maybe just putting the old deb

Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement

2012-06-14 Thread David Woodhouse
On Tue, 2012-06-12 at 15:18 +0200, Ralf Jung wrote: > [1339506419.612035] [nm-vpn-connection.c:934] get_secrets_cb(): > Failed > to request VPN secrets #3: (6) No agents were available for this request. I'm not entirely sure when plasma-widget-networkmanagement registers its NM VPN agent. This

Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement

2012-06-12 Thread Ralf Jung
Hi, I had quite some trouble getting the current openconnect installed without messing my system up (that is, compiling a Debian package for it)... and apparently I did something wrong, or it doesn't work: After also patching and installing plasma-widget-networkmanagement, connecting to the VPN

Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement

2012-06-07 Thread Ralf Jung
Hi, On Friday 01 June 2012 03:04:29 David Woodhouse wrote: > On Mon, 2012-05-28 at 13:14 +0200, Ralf Jung wrote: > > > That said, I'm working on porting to GnuTLS anyway. > > > > That's good news. Let me know if I can help testing :) > > http://lists.infradead.org/pipermail/openconnect-devel/201

Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement

2012-06-07 Thread David Woodhouse
On Thu, 2012-06-07 at 12:16 +0200, Ralf Jung wrote: > So the next step would be to change the KDE openconnect NM plugin to use the > GnuTLS backend of openconnect instead of the OpenSSL one? Currently the > backend also uses some stuff directly from OpenSSL, I do not know why that is > needed.

Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement

2012-05-31 Thread David Woodhouse
On Mon, 2012-05-28 at 13:14 +0200, Ralf Jung wrote: > > That said, I'm working on porting to GnuTLS anyway. > That's good news. Let me know if I can help testing :) http://lists.infradead.org/pipermail/openconnect-devel/2012-May/000572.html -- dwmw2 smime.p7s Description: S/MIME cryptographic

Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement

2012-05-28 Thread David Woodhouse
On Mon, 2012-05-28 at 13:14 +0200, Ralf Jung wrote: > > >* 6. Redistributions of any form whatsoever must retain the following > >*acknowledgment: > >*"This product includes software developed by the OpenSSL Project > >*for use in the OpenSSL Toolkit (http://www.openssl

Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement

2012-05-28 Thread Ralf Jung
Hi, > > According to the copyright headers and the git log, you are the main and > > actually almost the only author of that plugin. Is that correct, and if > > yes, would you be willing to add a license extension as stated in [1] to > > the files, so they can be linked with OpenSSL? > > Like lib

Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement

2012-05-28 Thread Michael Biebl
On 28.05.2012 12:21, Ralf Jung wrote: > Hi Ilia, > > the openconnect vpn module of the plasma widget for networkmanagement links > against OpenSSL, which has some problematic licensing consequences [1]. This > prevents the module from being enabled in Debian [2]. The openconnect vpn module is n

Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement

2012-05-28 Thread David Woodhouse
On Mon, 2012-05-28 at 12:21 +0200, Ralf Jung wrote: > According to the copyright headers and the git log, you are the main and > actually almost the only author of that plugin. Is that correct, and if yes, > would you be willing to add a license extension as stated in [1] to the > files, > so t

Bug#669702: OpenSSL and Openconnect VPN in plasma networkmanagement

2012-05-28 Thread Ralf Jung
Hi Ilia, the openconnect vpn module of the plasma widget for networkmanagement links against OpenSSL, which has some problematic licensing consequences [1]. This prevents the module from being enabled in Debian [2]. The only part of network manager directly linking with OpenSSL is that plugin -