Bug 672380

Summary: Regression in openvpn support moving from 0.9-0.30 --> 0.9-0.31
Product: [Fedora] Fedora Reporter: Carl Roth <roth>
Component: kde-plasma-networkmanagementAssignee: Rex Dieter <rdieter>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 14CC: kevin, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-13 15:06:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Carl Roth 2011-01-25 00:16:21 UTC 
Description of problem:

Connections to my openvpn server as of 0.9-0.31 are no longer working.  The syslog reports "No VPN Secrets!"

I'm connecting using the following parameters:

- password-based, with a CA file
- LZO compression
- TAP device
- everything else is left to defaults

Version-Release number of selected component (if applicable):

kde-plasma-networkmanagement-openvpn-0.9-0.31

How reproducible:

Always

Steps to Reproduce:
1. Create a VPN profile (in this case, password-based, with a CA file)
2. Try to connect
3.
  
Actual results:

Client does not connect.  Syslog messages report "No VPN Secrets!" even though a password was entered into the VPN connection creation dialog.

Expected results:


Additional info:

I trolled around koji for a bit to find the latest working version (this same server worked fine for me in F13 and F14 prior).

The last working version I found was 0.9-0.30.
Versions 0.9-0.31 and 0.9-0.32 do not work.

My workaround is to use the 0.9-0.30 version, and to (try to) ignore YUM updates for now.
Comment 1 Rex Dieter 2011-01-27 14:41:58 UTC 
That's too bad, these more recent snapshots were intended to improve vpn support (not regress), see
http://bugs.kde.org/244416
for example

Could you report this upstream to bugs.kde.org ?
Comment 2 Rex Dieter 2011-08-13 15:06:38 UTC 
upstream marked fixed, should be so in recent snapshot updates.