Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default SELinux context is incorrect. #68

Closed
kalvaer opened this issue Nov 8, 2017 · 3 comments
Closed

Default SELinux context is incorrect. #68

kalvaer opened this issue Nov 8, 2017 · 3 comments

Comments

@kalvaer
Copy link

kalvaer commented Nov 8, 2017

As per cvmfs/cvmfs#549
CVMFS now has a different default context type.
With SELinux enabled, this can cause CVMFS to fail.

ie:

Notice: /Stage[main]/Cvmfs::Install/File[/build1/cvmfs]/ensure: created
Notice: Applied catalog in 20.84 seconds
[root@pmjptppyum6 ~]# cvmfs_config chksetup
Warning: SELinux enabled, but cache directory (/build1/cvmfs) labeled 'var_lib_t' instead of 'cvmfs_cache_t'
[root@pmjptppyum6 ~]# cvmfs_config probe
Probing /cvmfs/atlas-condb.cern.ch... Failed!
Probing /cvmfs/atlas-nightlies.cern.ch... Failed!
Probing /cvmfs/atlas.cern.ch... Failed!

Patch file attached

set_default_secontext.patch.txt

@traylenator
Copy link
Contributor

@jblomer had a look through changelog but could not see when and where changed?

@jblomer
Copy link
Contributor

jblomer commented Nov 8, 2017

@traylenator This was part of cvmfs 2.1.20, there is a changelog entry

Use custom cvmfs_cache_t SELinux label for the cache directory (CVM-644)

@olifre
Copy link
Contributor

olifre commented May 22, 2018

Hi,
any progress on this?
It does not seem to have an actual negative effect, we are running stratum 0, stratum 1 and clients with SELinux in enforcing mode without issues, but this still looks like a bug which is simple to fix.

traylenator added a commit that referenced this issue Jun 28, 2018
Fixes #68 Correct selinux context for cache
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants