Description of problem: configuring vpnc, but vpnc didn't have access to the file. Additional info: libreport version: 2.0.18 kernel: 3.6.9-2.fc17.x86_64 description: :SELinux is preventing /usr/sbin/vpnc from 'read' accesses on the file /home/olsam/certificate/deutsche-telekom-root-ca-2.pem. : :***** Plugin catchall (100. confidence) suggests *************************** : :If you believe that vpnc should be allowed read access on the deutsche-telekom-root-ca-2.pem 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 vpnc /var/log/audit/audit.log | audit2allow -M mypol :# semodule -i mypol.pp : :Additional Information: :Source Context system_u:system_r:vpnc_t:s0 :Target Context unconfined_u:object_r:user_home_t:s0 :Target Objects /home/olsam/certificate/deutsche-telekom-root- : ca-2.pem [ file ] :Source vpnc :Source Path /usr/sbin/vpnc :Port <Unknown> :Host (removed) :Source RPM Packages vpnc-0.5.3-14.svn457.fc17.x86_64 :Target RPM Packages :Policy RPM selinux-policy-3.10.0-161.fc17.noarch :Selinux Enabled True :Policy Type targeted :Enforcing Mode Enforcing :Host Name (removed) :Platform Linux (removed) 3.6.9-2.fc17.x86_64 #1 SMP Tue Dec : 4 13:26:04 UTC 2012 x86_64 x86_64 :Alert Count 1 :First Seen 2012-12-10 17:31:07 CET :Last Seen 2012-12-10 17:31:07 CET :Local ID a81fa5dc-7c46-4edf-93e4-28ed5dfb926e : :Raw Audit Messages :type=AVC msg=audit(1355157067.193:304): avc: denied { read } for pid=14119 comm="vpnc" name="deutsche-telekom-root-ca-2.pem" dev="dm-2" ino=50070740 scontext=system_u:system_r:vpnc_t:s0 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file : : :type=SYSCALL msg=audit(1355157067.193:304): arch=x86_64 syscall=open success=no exit=EACCES a0=7fe865a8c140 a1=0 a2=7fffc4dd6bb8 a3=25fc2976 items=0 ppid=14117 pid=14119 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=vpnc exe=/usr/sbin/vpnc subj=system_u:system_r:vpnc_t:s0 key=(null) : :Hash: vpnc,vpnc_t,user_home_t,file,read : :audit2allow : :#============= vpnc_t ============== :allow vpnc_t user_home_t:file read; : :audit2allow -R : :#============= vpnc_t ============== :allow vpnc_t user_home_t:file read; :
Created attachment 660955 [details] File: type
Created attachment 660956 [details] File: hashmarkername
Can you move this certificate to either ~/.pki or ~/.cert WHich will have proper labeling for it. matchpathcon ~/.pki /home/dwalsh/.pki staff_u:object_r:home_cert_t:s0
Well, sure. I'm not sure what I think about the fix, but if that's how things are done, then I'll guess I'll do them that way.
Well you could change the default labeling for ~/certificates to be home_cert_t, but if it is easy to move to one of these directories, that would be better.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.