Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
SELinux System Administration, Third Edition

You're reading from   SELinux System Administration, Third Edition Implement mandatory access control to secure applications, users, and information flows on Linux

Arrow left icon
Product type Paperback
Published in Dec 2020
Publisher Packt
ISBN-13 9781800201477
Length 458 pages
Edition 3rd Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Sven Vermeulen Sven Vermeulen
Author Profile Icon Sven Vermeulen
Sven Vermeulen
Arrow right icon
View More author details
Toc

Table of Contents (22) Chapters Close

Preface 1. Section 1: Using SELinux
2. Chapter 1: Fundamental SELinux Concepts FREE CHAPTER 3. Chapter 2: Understanding SELinux Decisions and Logging 4. Chapter 3: Managing User Logins 5. Chapter 4: Using File Contexts and Process Domains 6. Chapter 5: Controlling Network Communications 7. Chapter 6: Configuring SELinux through Infrastructure-as-Code Orchestration 8. Section 2: SELinux-Aware Platforms
9. Chapter 7: Configuring Application-Specific SELinux Controls 10. Chapter 8: SEPostgreSQL – Extending PostgreSQL with SELinux 11. Chapter 9: Secure Virtualization 12. Chapter 10: Using Xen Security Modules with FLASK 13. Chapter 11: Enhancing the Security of Containerized Workloads 14. Section 3: Policy Management
15. Chapter 12: Tuning SELinux Policies 16. Chapter 13: Analyzing Policy Behavior 17. Chapter 14: Dealing with New Applications 18. Chapter 15: Using the Reference Policy 19. Chapter 16: Developing Policies with SELinux CIL 20. Assessments 21. Other Books You May Enjoy

Chapter 7

  1. The unit files in /usr/lib/systemd/system are managed by the Linux distribution itself. Whenever a new update to the software is deployed on the system, these files are overwritten.

    Modifications to unit files should be placed in /etc/systemd/system instead, as they overrule the settings in /usr/lib/systemd, and software deployments should not place any of their unit files in that location.

  2. The application is tmpfiles, and is part of the systemd suite. To have it reset a context, a configuration file has to be created (in /etc/tmpfiles.d for locally defined changes) and use the z directive (to reset the context of a single file) or the Z directive (to recursively set the context of an entire directory).
  3. The journalctl command allows filtering on variables that it obtained from the event itself. One of these variables is the SELinux context of the service that generated the event.

    To filter on a particular value, you use the variable name as an argument to the journalctl...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime