SELinux: please lie to me! 😭
This package provides a fake selinux module. This package mocked selinux module and
will always pretend SELinux is not enabled on the system.
But why? 😕
If your system runs SELinux and run Ansible in a virtualenv you will probably face this error:
Aborting, target uses selinux but python bindings (libselinux-python) aren't installed!
But what about the regular selinux package from Pypi?
You system comes with a python3-libselinux package that was built using on specific Python version.
For instance, on Fedora 34 it's Python 3.9. The same binary package may work fine with another Python
version, but it's not always the case.
Example with the selinux shim from pypi
In this example on Fedora 34, we cannot use the selinux shim package because Python 3.6 cannot load the system selinux binary for Python 3.9:
$ virtualenv -p python3.6 ~/tmp/my-venv-py36
(...)
$ ~/tmp/my-venv-py36/bin/pip install selinux
Collecting selinux
Using cached selinux-0.2.1-py2.py3-none-any.whl (4.3 kB)
Requirement already satisfied: setuptools>=39.0 in ./tmp/my-venv-py36/lib/python3.6/site-packages (from selinux) (53.0.0)
Collecting distro>=1.3.0
Using cached distro-1.5.0-py2.py3-none-any.whl (18 kB)
Installing collected packages: distro, selinux
Successfully installed distro-1.5.0 selinux-0.2.1
WARNING: You are using pip version 21.0.1; however, version 21.1.3 is available.
You should consider upgrading via the '/home/goneri/tmp/my-venv-py36/bin/python -m pip install --upgrade pip' command.
$ ~/tmp/my-venv-py36/bin/python -m selinux
Traceback (most recent call last):
File "/usr/lib64/python3.6/runpy.py", line 183, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
File "/usr/lib64/python3.6/runpy.py", line 142, in _get_module_details
return _get_module_details(pkg_main_name, error)
File "/usr/lib64/python3.6/runpy.py", line 109, in _get_module_details
__import__(pkg_name)
File "/home/goneri/tmp/my-venv-py36/lib/python3.6/site-packages/selinux/__init__.py", line 104, in <module>
check_system_sitepackages()
File "/home/goneri/tmp/my-venv-py36/lib/python3.6/site-packages/selinux/__init__.py", line 95, in check_system_sitepackages
success = add_location(candidate)
File "/home/goneri/tmp/my-venv-py36/lib/python3.6/site-packages/selinux/__init__.py", line 65, in add_location
reload(sys.modules["selinux"])
File "/usr/lib64/python3.6/importlib/__init__.py", line 166, in reload
_bootstrap._exec(spec, module)
File "/usr/lib64/python3.9/site-packages/selinux/__init__.py", line 13, in <module>
from . import _selinux
ImportError: cannot import name '_selinux'
Example with selinux_please_lie_to_me
$ virtualenv -p python3.6 venv
$ source venv/bin/active
$ pip install selinux_please_lie_to_me
$ python3 -c 'import selinux; print(f"SELinux is enabled: {selinux.is_selinux_enabled()}, (which is probably a lie 🤫)")'
SELinux is enabled: False, (which is probably a lie 🤫)
What does this break?
Since, we pretend selinux is disabled, we won't do any SELinux specific operation.
Metadata
Release files for selinux-please-lie-to-me 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| selinux_please_lie_to_me-1.0.1.tar.gz | 3.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| selinux_please_lie_to_me-1.0.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 7.6 kB
Release files / selinux_please_lie_to_me-1.0.1.tar.gz
| Download URL | selinux_please_lie_to_me-1.0.1.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
424c41756977338c263d624ffe5377c2a300e1074dccfd1486bc793c085aefbb
|
|
BLAKE2b-256 checksum How to use checksums |
66db210919df4457f5822b8e6a9e0238b9cf64fb6076014d274351fe41991398
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.5.0.1 requests/2.25.1 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.61.1 CPython/3.9.6
|
Release files / selinux_please_lie_to_me-1.0.1-py2.py3-none-any.whl
| Download URL | selinux_please_lie_to_me-1.0.1-py2.py3-none-any.whl |
|---|---|
| Size | 3.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
b61ab96bd813e4d52bf6d2095723c4d19d292aed68183375bc96bf70b700d7ba
|
|
BLAKE2b-256 checksum How to use checksums |
7b22128b09e93520788bcd711887d921e98e462af372456ffea4ee033ec1a9b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.5.0.1 requests/2.25.1 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.61.1 CPython/3.9.6
|
Security for selinux-please-lie-to-me 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.