did you give a try to the knetworkmanager plugin ?

CC: (none) => balcaen.john

Yeah I did.  I also tried kvpnc.  Here are the issues:

1) I can't just use openvpn with a config file because my provider uses name/password authentication, and openvpn as shipped as an rpm disallows name/password reading from a file.  Since it can't  read the password from a file and it is not an interactive program, it stops.

2) I can't use knetworkmanager as it is configured for mageia because it does not have the option of simple user/password as an authorization option.  

Oddly, Fedora, *does* have simple user/password as an option in its openvpn support for knetwork manager.  Since I need vpn, I have uninstalled mageia for the moment and have installed fedora, and openvpn is working fine.  

Basically, mageia's knetwork manager with openvpn support allowed two authorization options, as I remember (I haven't re-installed mageia as a virtual machine yet, so I don't have it up).  I think it was just pre-shared key and X.509 certificate.  The knetwork manager with fedora also has the option "password" which is what my provider needs.

hum if you're talking about Fedora 15,then we're providing the same openvpn plugin.
As far as i know there's no login/password only option for openvpn, you need to provide the CA file, the user certificate, the key certificate & eventually the password for this key certificate.
Are you sure you're not eventually talking about the vpnc plugin for (the CISCO VPN) which is indeed working with a login/pass.

Regards,

Nope.  It's openvpn -- I'm using it now.  To use login/password you use the option auth-user-pass-verify, I believe (though I'm certainly no openvpn expert).  To attempt to put that in a file, you can add auth-user-pass <filename> in the client.conf file.   

The way it's set up for me, I have a CA file and a TLS key, but no user certificate.

The client configuration file is below, as provided by my service provider.  Note that it uses auth-user-pass, which will not work with the default openvpn rpm.  Thus, I have to put in my username and password using a gui.

client
script-security 2
up /etc/openvpn/update-resolv-conf
down /etc/openvpn/update-resolv-conf
ns-cert-type server
persist-key
persist-tun
remote service.provider.com
dev tun1
tun-mtu 1500
ca ca.crt
auth-user-pass aup
tls-client
tls-auth ta.key 1
tls-exit
cipher BF-CBC
ping 10
comp-lzo
verb 4
port 443
proto tcp

So you're not using fedora 15? which version is it?
What do you mean with the default openvpn rpm? the knetworkmanager-openvpn ?, the networkmanager-openvpn ? 
i'll try to package gopenvpn this week

URL: (none) => http://gopenvpn.sourceforge.net/
Assignee: bugsquad => balcaen.john

Sorry, I'm not being clear.  Yes, I'm using Fedora 15.  The "nope" was in response to the possibility that I was using the Cisco vpn.

By the default openvpn rpm, I mean the openvpn rpm that comes with mageia.  For the fedora I'm running right now, it's

openvpn-2.1.4-1.fc15.i686.rpm

The kde/NetworkManager packages are front ends to openvpn, and have it as a dependency, as I recall, but do not themselves implement it.   The ability to read username/password from a file is a compiler option for openvpn, and the default is not to allow it.  That is how the openvpn that is distributed as an rpm in mageia is compiled, i.e. without the "enable-password-save" configure option turned on.

I'll reinstall mageia on one of my boxes tomorrow and send you a screenshot of the difference.

ok, i just push a new openvpn package with this switch enable :)

@ William

Are you content with openvpn as it is now, so that you don't need gopenvpn anymore and we can close this request?

Keywords: (none) => NEEDINFO
CC: (none) => marja11
Summary: Request for gopenvpn => gopenvpn (got maybe solved by new openvpn)

(In reply to comment #8)
> @ William
> 
> Are you content with openvpn as it is now, so that you don't need gopenvpn
> anymore and we can close this request?

No response, apparently you agree with closing

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX