Bug 1473904 - strongswan missing rules/policies? systemd service would not start
strongswan missing rules/policies? systemd service would not start
Status: NEW
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
26
x86_64 Linux
unspecified Severity urgent
: ---
: ---
Assigned To: Lukas Vrabec
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-22 04:33 EDT by lejeczek
Modified: 2017-07-22 04:33 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description lejeczek 2017-07-22 04:33:59 EDT
Description of problem:

...
can't execv(/usr/libexec/strongswan/charon,...): Permission denied
charon has died -- restart scheduled (5sec)
charon refused to be started
charon has died -- restart scheduled (5sec)
charon refused to be started
...

...
type=AVC msg=audit(1500712140.826:554): avc:  denied  { execute_no_trans } for  pid=16906 comm="starter" path="/usr/libexec/strongswan/charon" dev="dm-1" ino=2243357 scontext=system_u:system_r:ipsec_t:s0 tcontext=system_u:object_r:ipsec_exec_t:s0 tclass=file permissive=0

	Was caused by:
		Missing type enforcement (TE) allow rule.

		You can use audit2allow to generate a loadable module to allow this access.

type=AVC msg=audit(1500712145.830:555): avc:  denied  { execute_no_trans } for  pid=16910 comm="starter" path="/usr/libexec/strongswan/charon" dev="dm-1" ino=2243357 scontext=system_u:system_r:ipsec_t:s0 tcontext=system_u:object_r:ipsec_exec_t:s0 tclass=file permissive=0
...

Version-Release number of selected component (if applicable):

strongswan-5.5.0-3.fc26.x86_64
selinux-policy-3.13.1-260.1.fc26.noarch
strongswan-charon-nm-5.5.0-3.fc26.x86_64
selinux-policy-targeted-3.13.1-260.1.fc26.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Note You need to log in before you can comment on or make changes to this bug.