Bug 170890 - NetworkManager-vpnc and SELinux problem returns
NetworkManager-vpnc and SELinux problem returns
Product: Fedora
Classification: Fedora
Component: NetworkManager-vpnc (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Denis Leroy
Depends On:
Blocks: FC5Target
  Show dependency treegraph
Reported: 2005-10-14 23:09 EDT by Martin C. Messer
Modified: 2007-11-30 17:11 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-05 13:54:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Martin C. Messer 2005-10-14 23:09:10 EDT
Description of problem:

Same symptoms as bug 163405. Using setenforce 0 allows the VPN connection to
continue without /var/log/messages error (see below).

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


How reproducible:


Actual results:

Oct 14 22:58:02 localhost NetworkManager: <WARNING>       (): VPN failed for
service 'org.freedesktop.NetworkManager.vpnc', signal 'ConnectFailed', with
message 'The VPN login failed because the VPN program could not connect to the
VPN server.'.

Expected results:

VPN connection (which happens with 'setenforce 0').

Additional info:
Comment 1 Martin C. Messer 2005-10-15 20:36:56 EDT
I failed to mention a key piece of info:


Supposedly this problem was fixed with version 1.25.3-11 of that package. Not
sure if that means the bug is there or in NM.
Comment 2 Misha Kononov 2006-02-20 14:09:04 EST
Still experiencing this bug. Also note that the bug persists with SELinux
running in passive mode, though not with it disabled. Also, the symptoms do not
occur when running the NetworkManager daemon in CLI with --no-daemon. 
Comment 3 Daniel Walsh 2006-03-04 10:31:09 EST
Are you seeing any AVC messages in /var/log/audit/audit.log? or /var/log/messages?
Comment 4 Daniel Walsh 2006-03-08 11:55:07 EST
This is not an SELinux problem at this point.
Comment 5 Denis Leroy 2006-09-28 19:36:35 EDT
Taking ownership.
Comment 6 Warren Togami 2007-10-05 13:54:19 EDT
This was fixed long ago.

Note You need to log in before you can comment on or make changes to this bug.