[needs-packaging] gopenvpn

Bug #220362 reported by Helmuth Gronewold on 2008-04-21
This bug affects 3 people
Affects Status Importance Assigned to Milestone

Bug Description

Since Network-Manager lacks support of PKCS12 and multiple connections, include gopenvpn from http://gopenvpn.sourceforge.net/
This should be a wishlist-bug.

Helmuth Gronewold (cisa) on 2008-04-21
description: updated
trollord (trollenlord) wrote :

Add the missing functionality.

Alexander Sack (asac) wrote :

this is a needs packaging bug.

Changed in network-manager:
importance: Undecided → Wishlist
bojo42 (bojo42) wrote :

hi there, i just made a first debian package of openvpn in my ppa. hope that helps to get this starting here :)

bojo42 (bojo42) wrote :

alright i redid the package to clean up the first mess. so i separated the source and modifications, meaning i included dpatch for the patches to support OpenVPN v2.1 rc7+ from http://ubuntuforums.org/showthread.php?t=1021592 and resolved the needed procedure for autogen&autoheader in debian/rules. beside that i uuencoded the icon, added a man page and made a bit love with lintian regarding all those warnings.

so i would be pleased if someone could give me some feedback on the packaging :) just grab https://launchpad.net/%7Ebojo42/+archive/ppa/+files/gopenvpn_0.0.svn20090325-0ubuntu1~ppa1.dsc

bojo42 (bojo42) wrote :

i just had an additional thought regarding the current behaviour of openvpn on intrepid. so when you go with the default configuration of openvpn in /etc/default/openvpn a client.conf in /etc/openvpn gets autostarted.

that is a bit problematic, as you have a gui to control openvpn but by default your system tries to connect even if your new gopenvpn hasn't demanded it. usability wise this is confusing. of course we can disable this behaviour manually by setting in /etc/default/openvpn, but i think we should do this via the packaging script in gopenvpn.

the downside is that the gopenvpn package would interfere with the default settings of openvpn, so installing gopenvpn would alter a current command line setup. from my point of view it seems acceptable that a gui goes first in the case of conflicting default settings and advanced cli users shouldn't have big problems with that. but what do you think, should we integrate a different default configuration to openvpn in the package?

sefs (sefsinc) wrote :

What is the status of this, NetworkManager is dropping the ball in openvpn connectivity. Or is there any other gui for linux we can use that actually works, and has a deb?


Jochen Fahrner (jofa) wrote :

Since NetworkManagers OpenVPN plugin does not really work, please include some other package (like this) to make OpenVPN working on Ubuntu.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers