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? -- [needs-packaging] gopenvpn https://bugs.launchpad.net/bugs/220362 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
