From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008061712 Fedora/3.0-1.fc9 Firefox/3.0 Description of problem: I have been using vpnc (VPNC-0.5.1-5.fc9(i386)) in Fedora9 (2.6.25-14.fc9.i686) successfully with no problem. However, recently I updated the kernel to Fedora9 (2.6.25.6-55.fc9.i686) together with many other updates last week. Then when I start the vpnc procedure, I get the following messages: /etc/vpnc/vpnc-script: line 99: /sbin/ip: Permission denied /etc/vpnc/vpnc-script: line 100: /sbin/ip: Permission denied /etc/vpnc/vpnc-script: line 104: /sbin/ifconfig: Permission denied /etc/vpnc/vpnc-script: line 123: /sbin/ip: Permission denied /etc/vpnc/vpnc-script: line 123: /sbin/ip: Permission denied /etc/vpnc/vpnc-script: line 124: /sbin/ip: Permission denied /etc/vpnc/vpnc-script: line 133: /sbin/ip: Permission denied /etc/vpnc/vpnc-script: line 134: /sbin/ip: Permission denied /etc/vpnc/vpnc-script: line 135: /sbin/ip: Permission denied VPNC started in background (pid: 3127)... and the vpnc connection did not work for the intended destination. I tried to boot the system with the older kernel of Fedora 9 (2.6.25-14.fc9.i686), but now the same error message came out. How do we fix this bug? I am attaching the 'ausearch -m AVC' dump as suggested by tmraz with a cc to dwash. C. Y. Wong Version-Release number of selected component (if applicable): kernel-2.6.25.6-55.fc9(i686) How reproducible: Always Steps to Reproduce: 1.I invoke vpnc as a superuser. I have also already provided a default.conf in /etc/vpnc subdirectory. It always worked a few weeks ago with (kernel-2.6.25-14.fc9(i686). Actual Results: 2. But now, with the new upgrade to Fedora9 (2.6.25.6-55.fc9.i686), I got the above message as stated in my Description. 3.I cannot reach my intended connection using ssh or sftp. Expected Results: I should be able to reach my ssh or sftp destination and tunnel to that site. Additional info: I am attaching the ausearch dump as suggested by tmraz
Created attachment 310586 [details] dump from 'ausearch -m AVC'
Unfortunately I don't see any related AVCs in the dump. Can you try cleaning up the /var/log/audit/audit.log file and run 'setenforce 0' and retry the vpnc connection? If that helps it is really SELinux related problem and has to be fixed in the policy. Dan, were there any recent changes related to vpnc or ip and ifconfig in SELinux policy?
Thanks Tomas! I clean up /var/log/audit/audit.log and run /usr/sbin/setenforce 0 and then try the vpnc as suggested by Tomas. Now, the vpnc works and the connection gets to the intended destination as it should. So, it seems that this 'setenforce 0' works. Now, I guess we fix this 'SELinux related problem and has to be fixed in the policy'. C.Y. Wong
Can you now attach the 'ausearch -m AVC' dump?
Created attachment 310608 [details] 'ausearch -m AVC' dump this is the 'ausearch -m AVC' dump attachment requested by tmraz. at 2008-06-30 11:39 EST. As I reported at 11:18 EST, the problem was rectified by doing 'setenforce 0' and then vpnc. I can then get the vpnc connection to the destination as I intended, with no error messages. But, I do not know whether you may like to fix this problem in vpnc so that we do not need to do 'setenforce 0' every time we use vpnc. Thanks. C. Y. Wong
The weird on this is that when I issued setenforce 0; vpnc; vpnc-disconnect; it worked and then setenforce 1; vpnc; vpnc-disconnect; it worked nice then too. Maybe behind this is only my lack of SELinux expertise and it's expected.
I installed the latest bug-update (07/01/2008): selinux-policy-3.3.1.72.fc9(noarch) and selinuc-policy-targetd-3.3.1.72.fc9(noarch). [I also installed the latest kernel 2.6.25.9-76.fc9(i686). But the kernel version probably does not seem to matter.] I was able to connect by vpnc to the intended destination without error messages. It appears that this problem of "vpnc does not connect and gives error messages" has been fixed.
This disappeared somehow, close it, then, somehow too.