Bug 454358

Summary: selinux denials to pppd when using Network Manager
Product: [Fedora] Fedora Reporter: Brian G. Anderson <bikehead>
Component: selinux-policyAssignee: Daniel Walsh <dwalsh>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 9CC: jkubin
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-02 11:52:25 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 Flags
AVC messages about pppd denials none

Description Brian G. Anderson 2008-07-07 22:48:29 UTC
Description of problem:
I have network manager (NM) setup to use my bluetooth phone as a mobile
broadband modem.  When I initiate a connection I get selinux failures about pppd
not be allowed to access "/var/run/pppd2.tdb".

I can sucessfully connect if I disable selinux or a I make a custom policy
(which is what I did).  I'll attach the avc messages I got in the log and that I
used to make my local policy

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

How reproducible:
Every time

Steps to Reproduce:
1. Setup a broadband connection needing ppp.
2. Try and connect using nm-applet
Actual results:
Connection fails and setroubleshooter emits failure warnings

Expected results:
Successful connection

Additional info:

Comment 1 Brian G. Anderson 2008-07-07 22:51:33 UTC
Created attachment 311209 [details]
AVC messages about pppd denials

Comment 2 Jiri Skala 2008-08-20 13:50:57 UTC
I tested following commands to allow this and it works at me:

# audit2allow -M mypol -l -i /var/log/audit/audit.log
# semodule -i mypol.pp

This issue should fix new release of selinux-policy.

Comment 3 Jiri Skala 2008-09-02 11:52:25 UTC
I tested it with selinux-policy-3.3.1-87.fc9.noarch and it works fine.

*** This bug has been marked as a duplicate of bug 249152 ***