Bug 753126

Summary: SELinux is preventing /usr/sbin/openvpn from 'open' accesses on the file user.crt.
Product: [Fedora] Fedora Reporter: Michael <michael>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: dominick.grift, dwalsh, mgrepl, michael
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard: setroubleshoot_trace_hash:73ccb83bce4b3f4db2a9082ea1604a7916298e9493bb312a19e5a8266c51e0c1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-11 15:49:58 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 Michael 2011-11-11 12:03:29 UTC
SELinux is preventing /usr/sbin/openvpn from 'open' accesses on the file majestyx.crt.

*****  Plugin catchall (100. confidence) suggests  ***************************

If you believe that openvpn should be allowed open access on the majestyx.crt file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep openvpn /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:openvpn_t:s0
Target Context                system_u:object_r:dosfs_t:s0
Target Objects                user.crt [ file ]
Source                        openvpn
Source Path                   /usr/sbin/openvpn
Port                          <Unbekannt>
Host                          (removed)
Source RPM Packages           openvpn-2.1.4-1.fc15
Target RPM Packages           
Policy RPM                    selinux-policy-3.9.16-44.fc15
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 2.6.40.6-0.fc15.i686 #1 SMP Tue Oct 4
                              00:51:19 UTC 2011 i686 i686
Alert Count                   2
First Seen                    Fr 11 Nov 2011 12:55:48 CET
Last Seen                     Fr 11 Nov 2011 13:01:44 CET
Local ID                      917fc7d7-4172-4967-b5d0-b232e8455bcc

Raw Audit Messages
type=AVC msg=audit(1321012904.748:59): avc:  denied  { open } for  pid=1515 comm="openvpn" name="majestyx.crt" dev=dm-1 ino=1054363 scontext=system_u:system_r:openvpn_t:s0 tcontext=system_u:object_r:dosfs_t:s0 tclass=file


type=SYSCALL msg=audit(1321012904.748:59): arch=i386 syscall=open success=no exit=EACCES a0=bff05ef4 a1=8000 a2=1b6 a3=0 items=0 ppid=1509 pid=1515 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=openvpn exe=/usr/sbin/openvpn subj=system_u:system_r:openvpn_t:s0 key=(null)

Hash: openvpn,openvpn_t,dosfs_t,file,open

audit2allow

#============= openvpn_t ==============
allow openvpn_t dosfs_t:file open;

audit2allow -R

#============= openvpn_t ==============
allow openvpn_t dosfs_t:file open;

Comment 1 Michael 2011-11-11 12:07:19 UTC
i cant login to any VPN. yes i have done this (for 2 differend VPN)

# grep openvpn /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Comment 2 Daniel Walsh 2011-11-11 14:49:03 UTC
Where is your cert file located.  It looks like it has a dosfs_t label which probably means you mv'd it off of a FAT file system.

If you run restorecon -v majestyx.crt, does it change the label?

Comment 3 Michael 2011-11-11 15:49:58 UTC
i run this at root -> restorecon -v user.crt

output is:

restorecon reset /home/michael/openvpn/CyberGhost_user_Linux/user.crt context system_u:object_r:dosfs_t:s0->unconfined_u:object_r:user_home_t:s0

But it did not work...

yes, i change the files between 2 pc whit an fat32 formatted usb-stick. 
for a second test i download the original files from the cyberghost account. 

result: IT WORKS !!! 

THX for Help, and a nice weekend

Comment 4 Daniel Walsh 2011-11-11 16:03:28 UTC
SELinux expects the cert files to be labelled home_cert_t, if you copy them to ~/.pki or ~/.cert they will be labeled as home_cert_t.



If not, then run restorecon on them in one of those directories.