Order of scripts run before bash starts
Clash Royale CLAN TAG#URR8PPP
I'm studying the scripts run before a bash shell started by the user starts.
As far as i understand, the order is:
- home/username/.bashrc (modifiable by user)
- /etc/bashrc (modifiable by root)
- /etc/profile.d (modifiable by root)
Does this mean that the user could change .bashrc to prevent the new shell from running bashrc and profile.d? isnt this a security problem if the admin wanted to run some script to prevent the user from doing something when a new shell is instantiated?
bash security
add a comment |
I'm studying the scripts run before a bash shell started by the user starts.
As far as i understand, the order is:
- home/username/.bashrc (modifiable by user)
- /etc/bashrc (modifiable by root)
- /etc/profile.d (modifiable by root)
Does this mean that the user could change .bashrc to prevent the new shell from running bashrc and profile.d? isnt this a security problem if the admin wanted to run some script to prevent the user from doing something when a new shell is instantiated?
bash security
2
You may compare your findings/understanding with what the manual says under the section "INVOCATION". Also, I can't think of a situation where an admin could or wanted to prevent the user from doing something in their.bashrc
file. Could you give a scenario? If the account is restricted in various ways, the user may be given a restricted shell (see "RESTRICTED SHELL" in the manual).
– Kusalananda
Dec 19 '18 at 15:47
This is a pretty nice article illustrating the flow through the different startup files.
– Benjamin W.
Dec 19 '18 at 16:10
@BenjaminW. Some of the stuff there depends heavily on how the default files (both under/etc
and in the user's home directory) are set up to source each other. This will differ between Unix systems. The best thing is to read one's own manual (which may be different between systems) and to read one's own files, both under/etc
and in one's home directory.
– Kusalananda
Dec 19 '18 at 16:39
@Kusalananda Agree – I do like the article to get at least an idea of what could happen, and as a template to trace the flow in your own setup.
– Benjamin W.
Dec 19 '18 at 17:00
add a comment |
I'm studying the scripts run before a bash shell started by the user starts.
As far as i understand, the order is:
- home/username/.bashrc (modifiable by user)
- /etc/bashrc (modifiable by root)
- /etc/profile.d (modifiable by root)
Does this mean that the user could change .bashrc to prevent the new shell from running bashrc and profile.d? isnt this a security problem if the admin wanted to run some script to prevent the user from doing something when a new shell is instantiated?
bash security
I'm studying the scripts run before a bash shell started by the user starts.
As far as i understand, the order is:
- home/username/.bashrc (modifiable by user)
- /etc/bashrc (modifiable by root)
- /etc/profile.d (modifiable by root)
Does this mean that the user could change .bashrc to prevent the new shell from running bashrc and profile.d? isnt this a security problem if the admin wanted to run some script to prevent the user from doing something when a new shell is instantiated?
bash security
bash security
edited Dec 19 '18 at 15:45
asked Dec 19 '18 at 15:38
Joaquin Brandan
1123
1123
2
You may compare your findings/understanding with what the manual says under the section "INVOCATION". Also, I can't think of a situation where an admin could or wanted to prevent the user from doing something in their.bashrc
file. Could you give a scenario? If the account is restricted in various ways, the user may be given a restricted shell (see "RESTRICTED SHELL" in the manual).
– Kusalananda
Dec 19 '18 at 15:47
This is a pretty nice article illustrating the flow through the different startup files.
– Benjamin W.
Dec 19 '18 at 16:10
@BenjaminW. Some of the stuff there depends heavily on how the default files (both under/etc
and in the user's home directory) are set up to source each other. This will differ between Unix systems. The best thing is to read one's own manual (which may be different between systems) and to read one's own files, both under/etc
and in one's home directory.
– Kusalananda
Dec 19 '18 at 16:39
@Kusalananda Agree – I do like the article to get at least an idea of what could happen, and as a template to trace the flow in your own setup.
– Benjamin W.
Dec 19 '18 at 17:00
add a comment |
2
You may compare your findings/understanding with what the manual says under the section "INVOCATION". Also, I can't think of a situation where an admin could or wanted to prevent the user from doing something in their.bashrc
file. Could you give a scenario? If the account is restricted in various ways, the user may be given a restricted shell (see "RESTRICTED SHELL" in the manual).
– Kusalananda
Dec 19 '18 at 15:47
This is a pretty nice article illustrating the flow through the different startup files.
– Benjamin W.
Dec 19 '18 at 16:10
@BenjaminW. Some of the stuff there depends heavily on how the default files (both under/etc
and in the user's home directory) are set up to source each other. This will differ between Unix systems. The best thing is to read one's own manual (which may be different between systems) and to read one's own files, both under/etc
and in one's home directory.
– Kusalananda
Dec 19 '18 at 16:39
@Kusalananda Agree – I do like the article to get at least an idea of what could happen, and as a template to trace the flow in your own setup.
– Benjamin W.
Dec 19 '18 at 17:00
2
2
You may compare your findings/understanding with what the manual says under the section "INVOCATION". Also, I can't think of a situation where an admin could or wanted to prevent the user from doing something in their
.bashrc
file. Could you give a scenario? If the account is restricted in various ways, the user may be given a restricted shell (see "RESTRICTED SHELL" in the manual).– Kusalananda
Dec 19 '18 at 15:47
You may compare your findings/understanding with what the manual says under the section "INVOCATION". Also, I can't think of a situation where an admin could or wanted to prevent the user from doing something in their
.bashrc
file. Could you give a scenario? If the account is restricted in various ways, the user may be given a restricted shell (see "RESTRICTED SHELL" in the manual).– Kusalananda
Dec 19 '18 at 15:47
This is a pretty nice article illustrating the flow through the different startup files.
– Benjamin W.
Dec 19 '18 at 16:10
This is a pretty nice article illustrating the flow through the different startup files.
– Benjamin W.
Dec 19 '18 at 16:10
@BenjaminW. Some of the stuff there depends heavily on how the default files (both under
/etc
and in the user's home directory) are set up to source each other. This will differ between Unix systems. The best thing is to read one's own manual (which may be different between systems) and to read one's own files, both under /etc
and in one's home directory.– Kusalananda
Dec 19 '18 at 16:39
@BenjaminW. Some of the stuff there depends heavily on how the default files (both under
/etc
and in the user's home directory) are set up to source each other. This will differ between Unix systems. The best thing is to read one's own manual (which may be different between systems) and to read one's own files, both under /etc
and in one's home directory.– Kusalananda
Dec 19 '18 at 16:39
@Kusalananda Agree – I do like the article to get at least an idea of what could happen, and as a template to trace the flow in your own setup.
– Benjamin W.
Dec 19 '18 at 17:00
@Kusalananda Agree – I do like the article to get at least an idea of what could happen, and as a template to trace the flow in your own setup.
– Benjamin W.
Dec 19 '18 at 17:00
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f489947%2forder-of-scripts-run-before-bash-starts%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2funix.stackexchange.com%2fquestions%2f489947%2forder-of-scripts-run-before-bash-starts%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
2
You may compare your findings/understanding with what the manual says under the section "INVOCATION". Also, I can't think of a situation where an admin could or wanted to prevent the user from doing something in their
.bashrc
file. Could you give a scenario? If the account is restricted in various ways, the user may be given a restricted shell (see "RESTRICTED SHELL" in the manual).– Kusalananda
Dec 19 '18 at 15:47
This is a pretty nice article illustrating the flow through the different startup files.
– Benjamin W.
Dec 19 '18 at 16:10
@BenjaminW. Some of the stuff there depends heavily on how the default files (both under
/etc
and in the user's home directory) are set up to source each other. This will differ between Unix systems. The best thing is to read one's own manual (which may be different between systems) and to read one's own files, both under/etc
and in one's home directory.– Kusalananda
Dec 19 '18 at 16:39
@Kusalananda Agree – I do like the article to get at least an idea of what could happen, and as a template to trace the flow in your own setup.
– Benjamin W.
Dec 19 '18 at 17:00