{"id":723,"date":"2009-07-24T05:54:56","date_gmt":"2009-07-23T19:54:56","guid":{"rendered":"http:\/\/nsrd.wordpress.com\/?p=723"},"modified":"2018-12-12T15:55:53","modified_gmt":"2018-12-12T05:55:53","slug":"using-selinux-with-networker","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2009\/07\/24\/using-selinux-with-networker\/","title":{"rendered":"Using SELinux with NetWorker"},"content":{"rendered":"

I’m not all that conversant with SELinux, and for the most part<\/em>, disable it on systems that I configure simply because these days 99% of the systems I configure are within a lab and already heavily firewalled. When NetWorker 7.5 came out and the release notes explicitly stated that SELinux was not supported, it seemed inevitable that my involvement with SELinux would continue to decrease.<\/p>\n

When SELinux was recently discussed on the NetWorker mailing list, I responded citing the release notes indicating it wasn’t supported. I was therefore surprised to discover there was a workaround. Responding to the thread, Rich Graves posted the following SELinux adjustments that are necessary to get NetWorker and SELinux working together. I present them unaltered, but can attest to having confirmed they do indeed work. Here’s what Rich had to say:<\/p>\n

This has worked for me for about a year, on both client and server. The textrel_shlib change is fairly common for proprietary binaries.<\/p>\n

semanage fcontext -a -t textrel_shlib_t “\/usr\/lib\/nsr(\/.*)?”
\nsemanage fcontext -a -t var_log_t “\/nsr\/logs(\/.*)?”
\nrestorecon -R \/usr\/lib\/nsr
\nrestorecon -R \/nsr\/logs<\/p>\n

Another approach for the logs is to edit syslog.conf and drop them in \/var\/log instead of \/nsr\/logs.<\/p><\/blockquote>\n

If you’re needing to work with NetWorker and SELinux, hopefully the above tips will help.<\/p>\n","protected":false},"excerpt":{"rendered":"

I’m not all that conversant with SELinux, and for the most part, disable it on systems that I configure simply…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[16,21],"tags":[873],"class_list":["post-723","post","type-post","status-publish","format-standard","hentry","category-networker","category-security","tag-selinux"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t