Can you restrict the actions of an unconfined_t process with a custom SELinux policy?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
Assuming you're running a Linux distro with SELinux enabled on it under enforcing mode, is it possible to write and compile a policy for it that restricts all unconfined_t processes running on the system from accessing certain resources (like specific files under a specifc directory, obviously marked with the appropriate custom labels)?
Or do I have to relabel these processes to run under a different context first before I can apply special policy rules to them as "unconfined_t" should never be confined by design?
linux selinux security-policy
add a comment |
Assuming you're running a Linux distro with SELinux enabled on it under enforcing mode, is it possible to write and compile a policy for it that restricts all unconfined_t processes running on the system from accessing certain resources (like specific files under a specifc directory, obviously marked with the appropriate custom labels)?
Or do I have to relabel these processes to run under a different context first before I can apply special policy rules to them as "unconfined_t" should never be confined by design?
linux selinux security-policy
add a comment |
Assuming you're running a Linux distro with SELinux enabled on it under enforcing mode, is it possible to write and compile a policy for it that restricts all unconfined_t processes running on the system from accessing certain resources (like specific files under a specifc directory, obviously marked with the appropriate custom labels)?
Or do I have to relabel these processes to run under a different context first before I can apply special policy rules to them as "unconfined_t" should never be confined by design?
linux selinux security-policy
Assuming you're running a Linux distro with SELinux enabled on it under enforcing mode, is it possible to write and compile a policy for it that restricts all unconfined_t processes running on the system from accessing certain resources (like specific files under a specifc directory, obviously marked with the appropriate custom labels)?
Or do I have to relabel these processes to run under a different context first before I can apply special policy rules to them as "unconfined_t" should never be confined by design?
linux selinux security-policy
linux selinux security-policy
asked Jan 27 at 17:23
AlexAlex
115
115
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1398982%2fcan-you-restrict-the-actions-of-an-unconfined-t-process-with-a-custom-selinux-po%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1398982%2fcan-you-restrict-the-actions-of-an-unconfined-t-process-with-a-custom-selinux-po%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown