Bug 1893545 - semanage refuse paths with space
Summary: semanage refuse paths with space
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: policycoreutils
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Lautrbach
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-01 18:08 UTC by Jonas Jonsson
Modified: 2021-05-25 16:58 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-05-25 16:58:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jonas Jonsson 2020-11-01 18:08:14 UTC
Description of problem:
I'm trying to set the public_content_t to a directory in order for both samba and httpd to have access to it with selinux in enforced mode.

semanage fcontext -a -t public_content_t "/mnt/media/My\ Dir(/.*)?"

Version-Release number of selected component (if applicable):
policycoreutils-python-utils-3.0-2.fc32.noarch

How reproducible:
Always

Steps to Reproduce:
1. Try to set file context on a path with spaces
2. Watch tool complain

Actual results:
ValueError: File specification can not include spaces

Expected results:
Working tool.

Additional info:
It looks like this was a fix some 10 years ago, https://bugzilla.redhat.com/show_bug.cgi?id=537754

Comment 1 Milos Malik 2020-11-02 08:04:54 UTC
The same issue is also reproducible on Fedora rawhide:

# rpm -qf `which semanage`
policycoreutils-python-utils-3.1-4.fc33.noarch
# semanage fcontext -a -t public_content_t "/mnt/media/My\ Dir(/.*)?"
ValueError: File specification can not include spaces
#

Comment 2 Milos Malik 2020-11-27 14:59:05 UTC
Test coverage for this bug exists in a form of PR:
 * https://src.fedoraproject.org/tests/selinux/pull-request/142

The PR waits for review.

Comment 3 Fedora Program Management 2021-04-29 16:43:06 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 '32'.

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 32 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.

Comment 4 Ben Cotton 2021-05-25 16:58:08 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.


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