Bring back the OpenVPN Desktop Client UI

[jdrews]

The OpenVPN Desktop Client (Also referred to as OpenVPN Connect Client) is significantly easier to use for non tech savvy users. Please bring it back!

For clarity I'm referring to the UI that looks like this:


I understand it was pulled for security reasons.
topic17732.html#p47591
http://cve.mitre.org/cgi-bin/cvename.cg ... -2014-9104

But it is way easier for the tech laymans of my company to use. We would really like to have it back. The current UI requires a bunch of right clicks and dropping files in folders, that many people don't understand. The old UI had a + button to add an .ovpn file and easy launching of connections by clicking squares, and easy disconnect by clicking 'disconnect' buttons. Plus it just looks better!

Thanks!

[Douglas]

I do admit this desktop client is pretty and easy to use for what it is.

[jdrews]

Where did this client come from? What is it's history? Google is coming up with blanks on those questions...

Also I'm curious to know why it was dropped in the first place. Besides the security issue, was there another reason why it was dropped? Was it impossible to patch the security flaw?

[kevinl]

I second this motion! The old GUI was a much more user-friendly interface to the OpenVPN client, especially for non-technical users, as well as looking better.

Ideally this GUI would have two modes of operation on Windows:
1. Open client VPN connections by running dynamic instances of openvpn.exe to connect the selected client config (this mode would require the GUI to be run as Administrator), and
2. Open client VPN connections by controlling the Windows OpenVPN service to connect the selected client config (this mode would NOT require the GUI to be run as Administrator).

Is the source code for the older GUI available as open source? I wouldn't mind having a go at getting this working.

[WitzEnd Computing]

I'm looking for #2. I need users to be able to click on a single download from the Connect page that will install the OpenVPN client in Windows which will then import their config file to the C:\Program Files (x86)\OpenVPN Technologies\OpenVPN Client\core\ and add a service parameter of --connect client.ovpn so that the service will automatically connect with their credentials on startup instead of requiring the user to login and connect. I know it would require local admin rights, but I don't think that will be an issue.
Has anyone already scripted this?