Ensure builtin command is run under pathological circumstances
Given a hostile environment such as:
builtin() { echo builtin function; }
command() { echo command function; }
type() { echo type function; }
unfunction(){ echo function unfunction; }
declare() { echo function declare; }
alias builtin=' echo builtin aliased #'
alias command=' echo command aliased #'
alias type=' echo type aliased #'
alias unfunction='echo unfunction aliased #'
alias declare=' echo declare aliased #'
Is it possible to access a builtin command? Eg, is it possible to do something like:
command builtin type echo
and still see:
echo is a shell builtin
Is possible for a hostile environment to be able to completely redefine things such that an underlying builtin, function or pathname could never be accessed?
bash shell zsh
add a comment |
Given a hostile environment such as:
builtin() { echo builtin function; }
command() { echo command function; }
type() { echo type function; }
unfunction(){ echo function unfunction; }
declare() { echo function declare; }
alias builtin=' echo builtin aliased #'
alias command=' echo command aliased #'
alias type=' echo type aliased #'
alias unfunction='echo unfunction aliased #'
alias declare=' echo declare aliased #'
Is it possible to access a builtin command? Eg, is it possible to do something like:
command builtin type echo
and still see:
echo is a shell builtin
Is possible for a hostile environment to be able to completely redefine things such that an underlying builtin, function or pathname could never be accessed?
bash shell zsh
unalias builtin; unset -f builtin
? I don't think this environment is hostile enough.
– Michael Homer
18 mins ago
add a comment |
Given a hostile environment such as:
builtin() { echo builtin function; }
command() { echo command function; }
type() { echo type function; }
unfunction(){ echo function unfunction; }
declare() { echo function declare; }
alias builtin=' echo builtin aliased #'
alias command=' echo command aliased #'
alias type=' echo type aliased #'
alias unfunction='echo unfunction aliased #'
alias declare=' echo declare aliased #'
Is it possible to access a builtin command? Eg, is it possible to do something like:
command builtin type echo
and still see:
echo is a shell builtin
Is possible for a hostile environment to be able to completely redefine things such that an underlying builtin, function or pathname could never be accessed?
bash shell zsh
Given a hostile environment such as:
builtin() { echo builtin function; }
command() { echo command function; }
type() { echo type function; }
unfunction(){ echo function unfunction; }
declare() { echo function declare; }
alias builtin=' echo builtin aliased #'
alias command=' echo command aliased #'
alias type=' echo type aliased #'
alias unfunction='echo unfunction aliased #'
alias declare=' echo declare aliased #'
Is it possible to access a builtin command? Eg, is it possible to do something like:
command builtin type echo
and still see:
echo is a shell builtin
Is possible for a hostile environment to be able to completely redefine things such that an underlying builtin, function or pathname could never be accessed?
bash shell zsh
bash shell zsh
asked 34 mins ago
Tom HaleTom Hale
6,85333694
6,85333694
unalias builtin; unset -f builtin
? I don't think this environment is hostile enough.
– Michael Homer
18 mins ago
add a comment |
unalias builtin; unset -f builtin
? I don't think this environment is hostile enough.
– Michael Homer
18 mins ago
unalias builtin; unset -f builtin
? I don't think this environment is hostile enough.– Michael Homer
18 mins ago
unalias builtin; unset -f builtin
? I don't think this environment is hostile enough.– Michael Homer
18 mins ago
add a comment |
0
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%2f497327%2fensure-builtin-command-is-run-under-pathological-circumstances%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 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.
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%2f497327%2fensure-builtin-command-is-run-under-pathological-circumstances%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
unalias builtin; unset -f builtin
? I don't think this environment is hostile enough.– Michael Homer
18 mins ago