Description of problem: libreswan appears to be attempting to access @FINALRUNDIR@ -- this variable is in "/usr/libexec/ipsec/setup" in 3.22-1.fc27 SELinux is preventing chmod from 'setattr' accesses on the directory /@FINALRUNDIR@. ***** Plugin restorecon (99.5 confidence) suggests ************************ If you want to fix the label. /@FINALRUNDIR@ default label should be default_t. Then you can run restorecon. The access attempt may have been stopped due to insufficient permissions to access a parent directory in which case try to change the following command accordingly. Do # /sbin/restorecon -v /@FINALRUNDIR@ ***** Plugin catchall (1.49 confidence) suggests ************************** If you believe that chmod should be allowed setattr access on the @FINALRUNDIR@ directory 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 'chmod' --raw | audit2allow -M my-chmod # semodule -X 300 -i my-chmod.pp Additional Information: Source Context system_u:system_r:ipsec_mgmt_t:s0 Target Context system_u:object_r:root_t:s0 Target Objects /@FINALRUNDIR@ [ dir ] Source chmod Source Path chmod Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-283.17.fc27.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 4.14.3-300.fc27.x86_64 #1 SMP Mon Dec 4 17:18:27 UTC 2017 x86_64 x86_64 Alert Count 2 First Seen 2017-12-11 21:27:07 EST Last Seen 2017-12-12 08:04:40 EST Local ID 570a59a5-0b08-4ff6-b400-83b6a66101f6 Raw Audit Messages type=AVC msg=audit(1513083880.586:256): avc: denied { setattr } for pid=2817 comm="chmod" name="@FINALRUNDIR@" dev="dm-1" ino=402665843 scontext=system_u:system_r:ipsec_mgmt_t:s0 tcontext=system_u:object_r:root_t:s0 tclass=dir permissive=1 Hash: chmod,ipsec_mgmt_t,root_t,dir,setattr Version-Release number of selected component: selinux-policy-3.13.1-283.17.fc27.noarch Additional info: component: selinux-policy reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.14.3-300.fc27.x86_64 type: libreport
This is some issue in ipsec.
Confirm it, same happen with ipsec
I'm experiencing this behavior also, appears to be preventing me from connecting to my l2tp/ipsec VPNs. Can someone suggest a workaround?
related to https://bugzilla.redhat.com/show_bug.cgi?id=1517427 ?
IPsec is currently broken under the 4.14 kernel (see https://bugzilla.redhat.com/show_bug.cgi?id=1526203).
Hm. I appear to be also experiencing this behavior under 4.13.9. https://paste.fedoraproject.org/paste/YnQIE00Lc9kXpS4wmuMQHg
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.