Hide Forgot
SELinux is preventing /usr/libexec/nm-openvpn-service from 'read' accesses on the file /home/adam/bin/AdamnrhiVPN/AmahiHDAClient.key. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that nm-openvpn-service should be allowed read access on the AmahiHDAClient.key 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 nm-openvpn-serv /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:NetworkManager_t:s0 Target Context unconfined_u:object_r:home_bin_t:s0 Target Objects /home/adam/bin/AdamnrhiVPN/AmahiHDAClient.key [ file ] Source nm-openvpn-serv Source Path /usr/libexec/nm-openvpn-service Port <Unknown> Host (removed) Source RPM Packages NetworkManager-openvpn-0.9.0-1.fc15 Target RPM Packages Policy RPM selinux-policy-3.9.16-39.fc15 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 2.6.40.6-0.fc15.x86_64 #1 SMP Tue Oct 4 00:39:50 UTC 2011 x86_64 x86_64 Alert Count 6 First Seen Tue 18 Oct 2011 10:15:38 AM CDT Last Seen Tue 18 Oct 2011 10:15:47 AM CDT Local ID a256bb01-af86-48eb-ad67-4bec1e78fcc8 Raw Audit Messages type=AVC msg=audit(1318950947.174:106): avc: denied { read } for pid=5160 comm="nm-openvpn-serv" name="AmahiHDAClient.key" dev=dm-2 ino=1443154 scontext=system_u:system_r:NetworkManager_t:s0 tcontext=unconfined_u:object_r:home_bin_t:s0 tclass=file type=SYSCALL msg=audit(1318950947.174:106): arch=x86_64 syscall=open success=no exit=EACCES a0=25a7e00 a1=0 a2=1b6 a3=1 items=0 ppid=840 pid=5160 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=nm-openvpn-serv exe=/usr/libexec/nm-openvpn-service subj=system_u:system_r:NetworkManager_t:s0 key=(null) Hash: nm-openvpn-serv,NetworkManager_t,home_bin_t,file,read audit2allow #============= NetworkManager_t ============== allow NetworkManager_t home_bin_t:file read; audit2allow -R #============= NetworkManager_t ============== allow NetworkManager_t home_bin_t:file read;
I think this is a simple issue really... I have a personal VPN connection and store the keys with my user's files. Shouldn't this type of access for network manager be allowed by default? Or perhaps there is a "better" place to put these keys? Though, I'm guessing that would require administrator access for any users to setup VPN connections with NetworkManager. adam
~/.pki or ~/.cert Should work. I would run restorecon ~/.cert ~/.pki After you move your files there.