Description of problem: Unable to start strongswan service Version-Release number of selected component (if applicable): strongswan-5.5.0-3.fc26.x86_64 selinux-policy-3.13.1-251.fc26.noarch How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: strongswan[4038]: can't execv(/usr/libexec/strongswan/charon,...): Permission denied strongswan[4038]: charon has died -- restart scheduled (5sec) Expected results: Additional info: SELinux is preventing starter from execute_no_trans access on the file /usr/libexec/strongswan/charon. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that starter should be allowed execute_no_trans access on the charon 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: # ausearch -c 'starter' --raw | audit2allow -M my-starter # semodule -X 300 -i my-starter.pp Additional Information: Source Context system_u:system_r:ipsec_t:s0 Target Context system_u:object_r:ipsec_exec_t:s0 Target Objects /usr/libexec/strongswan/charon [ file ] Source starter Source Path starter Port <Unknown> Host (none) Source RPM Packages Target RPM Packages strongswan-5.5.0-3.fc26.x86_64 Policy RPM selinux-policy-3.13.1-251.fc26.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (none) Platform Linux (none) 4.11.0-0.rc7.git0.1.fc26.x86_64 #1 SMP Mon Apr 17 18:09:42 UTC 2017 x86_64 x86_64 Alert Count 10 First Seen 2017-04-23 10:27:24 IDT Last Seen 2017-04-23 10:28:09 IDT Local ID fe541056-001d-4b89-8caa-0b5751e7326d Raw Audit Messages type=AVC msg=audit(1492932489.107:283): avc: denied { execute_no_trans } for pid=4125 comm="starter" path="/usr/libexec/strongswan/charon" dev="dm-0" ino=3416550 scontext=system_u:system_r:ipsec_t:s0 tcontext=system_u:object_r:ipsec_exec_t:s0 tclass=file permissive=0 Hash: starter,ipsec_t,ipsec_exec_t,file,execute_no_trans
Still present: selinux-policy-3.13.1-259.fc26.noarch strongswan-5.5.3-1.fc26.x86_64
This my local policy to make StrongSWAN work again: module local 1.0; require { type ipsec_t; type ipsec_exec_t; type var_run_t; class file { execute_no_trans }; class sock_file { unlink write }; } #============= ipsec_t ============== allow ipsec_t ipsec_exec_t:file execute_no_trans; allow ipsec_t var_run_t:sock_file { unlink write };
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 EOL if it remains open with a Fedora 'version' of '26'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 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 this bug is closed as described in the policy above. 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.