Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Consider the following unit file,

[Service]
User=tester
ExecStart=/bin/bash -c "touch /home/tester/foo"
RootDirectory=/opt/chroot/
ProtectHome=true

It declares ProtectHome=true and that should make /home read-only for the service. However if we run the service on current RHEL-7.3, it exists successfully and is able to create empty file foo. This is a bug, since /home shouldn't be writable. 

Version-Release number of selected component (if applicable):
systemd-219-30.el7_3.6.x86_64

How reproducible:
always

Steps to Reproduce:
1. write above unit file to /etc/systemd/system/test.service
2. create user named tester - useradd tester
3. reload systemd - systemctl daemon-reload
4. bind mount / to /opt/chroot - mkdir -p /opt/chroot && mount --bind / /opt/chroot
5. start the service - systemctl start test.service
6. get status of the service

Actual results:
Service exists successfully, file /opt/chroot/home/tester/foo exists

Expected results:
Service fails, file is not present

Additional info:
upstream fix,

https://github.com/systemd/systemd/commit/ee818b89f4890b3a00e93772249fce810f60811e

https://github.com/lnykryn/systemd-rhel/pull/94

fix merged to upstream staging branch ->
-> post

fix merged to upstream staging branch ->
https://github.com/lnykryn/systemd-rhel/commit/2b4894764e9e92ae9004524ed466b4bdf94b2a34
https://github.com/lnykryn/systemd-rhel/commit/ccf46ebc548054f876a418fc2e949a05a74a9c2a
-> post

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2297