Improper import of configuration file: TLS-auth key direction gets reversed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-openvpn (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-
When I import the attached configuration file, the key direction under 'Advanced -> TLS authentication' is not imported properly: Instead of '1' it is set to '0' which breaks the VPN connection. This works properly in Karmic with the same configuration file.
ProblemType: Bug
Architecture: amd64
CheckboxSubmission: de79b5a68af91fe
CheckboxSystem: d00f84de8a55581
Date: Sun Mar 7 15:30:48 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1)
Package: network-
ProcEnviron:
SHELL=/bin/bash
LANG=de_DE.utf8
ProcVersionSign
SourcePackage: network-
Uname: Linux 2.6.32-15-generic x86_64
tags: | added: regression-release |
Still there in Beta 1. The part from the configuration file, that I get from my university is 'tls-auth ta.key 1'. This should give a '1' as well in 'key direction', but instead I get a '0' when importing this file.