Disable feedback when typing password at a sudo prompt
When I type my password at a sudo command line prompt, it shows * for each keystroke recently. Is this a new default behaviour? How do I switch this off again?
There is no pwfeedback option set in my /etc/sudoers file. I am using Linux Mint 19 which is Ubuntu Bionic basically, package version of sudo is 1.8.21p2-3ubuntu1 and my sudo binary shows the same sha256 hash than the one in the package.
Thanks for any advice!
Inverted question of: Feedback when typing password at a sudo prompt
linux ubuntu command-line passwords sudo
asked Feb 11 at 10:18
1ng01ng0
13
add a comment |
When I type my password at a sudo command line prompt, it shows * for each keystroke recently. Is this a new default behaviour? How do I switch this off again?
There is no pwfeedback option set in my /etc/sudoers file. I am using Linux Mint 19 which is Ubuntu Bionic basically, package version of sudo is 1.8.21p2-3ubuntu1 and my sudo binary shows the same sha256 hash than the one in the package.
Thanks for any advice!
Inverted question of: Feedback when typing password at a sudo prompt
linux ubuntu command-line passwords sudo
asked Feb 11 at 10:18
1ng01ng0
13
add a comment |
When I type my password at a sudo command line prompt, it shows * for each keystroke recently. Is this a new default behaviour? How do I switch this off again?
There is no pwfeedback option set in my /etc/sudoers file. I am using Linux Mint 19 which is Ubuntu Bionic basically, package version of sudo is 1.8.21p2-3ubuntu1 and my sudo binary shows the same sha256 hash than the one in the package.
Thanks for any advice!
Inverted question of: Feedback when typing password at a sudo prompt
linux ubuntu command-line passwords sudo
asked Feb 11 at 10:18
1ng01ng0
13
When I type my password at a sudo command line prompt, it shows * for each keystroke recently. Is this a new default behaviour? How do I switch this off again?
There is no pwfeedback option set in my /etc/sudoers file. I am using Linux Mint 19 which is Ubuntu Bionic basically, package version of sudo is 1.8.21p2-3ubuntu1 and my sudo binary shows the same sha256 hash than the one in the package.
Thanks for any advice!
Inverted question of: Feedback when typing password at a sudo prompt
linux ubuntu command-line passwords sudo
linux ubuntu command-line passwords sudo
asked Feb 11 at 10:18
1ng01ng0
13
asked Feb 11 at 10:18
1ng01ng0
13
asked Feb 11 at 10:18
1ng01ng0
13
asked Feb 11 at 10:18
1ng01ng0
13
asked Feb 11 at 10:18
1ng01ng0
13
13
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I think you can get rid of the feedback by editing
the file /etc/sudoers.
Search for a line that may look like this:
Defaults env_reset,pwfeedback
and delete ,pwfeedback from the line. Take first a backup copy of it.
You may need to reset your terminal using the command reset.
If this does not work, another possibility is to rename the file
/etc/sudoers.d/pwfeedback to something else, keeping it just in case.
answered Feb 11 at 13:14
harrymcharrymc
261k14271577
Thanks for the hint, but as I wrote, there is no pwfeedback in mysudoersfile.
– 1ng0
Feb 11 at 13:30
You missed out on the last paragraph in my answer.
– harrymc
Feb 11 at 14:07
Sorry, but renaming the file will not help, it will be included in the sudoers anyway. Only deleting the file will fix the problem, as I wrote in my answer. Moreover, the name of the file causing the problem is actually 0pwfeedback.
– 1ng0
Feb 11 at 16:52
add a comment |
After some more research on files in the /etc/sudoers.d directory, I found the right answer here:
Linux Mint. How to set the terminal password to be invisible?
Is says:
"LinuxMint added the behavior in /etc/sudoers.d/0pwfeedback.
You could simply do like I did, delete the file as it contains only that adjustment:
sudo rm -rf /etc/sudoers.d/0pwfeedback"
Just renaming that file will not help.
answered Feb 11 at 13:36
1ng01ng0
13
add a comment |
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%2f1404382%2fdisable-feedback-when-typing-password-at-a-sudo-prompt%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I think you can get rid of the feedback by editing
the file /etc/sudoers.
Search for a line that may look like this:
Defaults env_reset,pwfeedback
and delete ,pwfeedback from the line. Take first a backup copy of it.
You may need to reset your terminal using the command reset.
If this does not work, another possibility is to rename the file
/etc/sudoers.d/pwfeedback to something else, keeping it just in case.
answered Feb 11 at 13:14
harrymcharrymc
261k14271577
Thanks for the hint, but as I wrote, there is no pwfeedback in mysudoersfile.
– 1ng0
Feb 11 at 13:30
You missed out on the last paragraph in my answer.
– harrymc
Feb 11 at 14:07
Sorry, but renaming the file will not help, it will be included in the sudoers anyway. Only deleting the file will fix the problem, as I wrote in my answer. Moreover, the name of the file causing the problem is actually 0pwfeedback.
– 1ng0
Feb 11 at 16:52
add a comment |
I think you can get rid of the feedback by editing
the file /etc/sudoers.
Search for a line that may look like this:
Defaults env_reset,pwfeedback
and delete ,pwfeedback from the line. Take first a backup copy of it.
You may need to reset your terminal using the command reset.
If this does not work, another possibility is to rename the file
/etc/sudoers.d/pwfeedback to something else, keeping it just in case.
answered Feb 11 at 13:14
harrymcharrymc
261k14271577
Thanks for the hint, but as I wrote, there is no pwfeedback in mysudoersfile.
– 1ng0
Feb 11 at 13:30
You missed out on the last paragraph in my answer.
– harrymc
Feb 11 at 14:07
Sorry, but renaming the file will not help, it will be included in the sudoers anyway. Only deleting the file will fix the problem, as I wrote in my answer. Moreover, the name of the file causing the problem is actually 0pwfeedback.
– 1ng0
Feb 11 at 16:52
add a comment |
I think you can get rid of the feedback by editing
the file /etc/sudoers.
Search for a line that may look like this:
Defaults env_reset,pwfeedback
and delete ,pwfeedback from the line. Take first a backup copy of it.
You may need to reset your terminal using the command reset.
If this does not work, another possibility is to rename the file
/etc/sudoers.d/pwfeedback to something else, keeping it just in case.
answered Feb 11 at 13:14
harrymcharrymc
261k14271577
I think you can get rid of the feedback by editing
the file /etc/sudoers.
Search for a line that may look like this:
Defaults env_reset,pwfeedback
and delete ,pwfeedback from the line. Take first a backup copy of it.
You may need to reset your terminal using the command reset.
If this does not work, another possibility is to rename the file
/etc/sudoers.d/pwfeedback to something else, keeping it just in case.
answered Feb 11 at 13:14
harrymcharrymc
261k14271577
answered Feb 11 at 13:14
harrymcharrymc
261k14271577
answered Feb 11 at 13:14
harrymcharrymc
261k14271577
answered Feb 11 at 13:14
harrymcharrymc
261k14271577
261k14271577
Thanks for the hint, but as I wrote, there is no pwfeedback in mysudoersfile.
– 1ng0
Feb 11 at 13:30
You missed out on the last paragraph in my answer.
– harrymc
Feb 11 at 14:07
Sorry, but renaming the file will not help, it will be included in the sudoers anyway. Only deleting the file will fix the problem, as I wrote in my answer. Moreover, the name of the file causing the problem is actually 0pwfeedback.
– 1ng0
Feb 11 at 16:52
add a comment |
Thanks for the hint, but as I wrote, there is no pwfeedback in mysudoersfile.
– 1ng0
Feb 11 at 13:30
You missed out on the last paragraph in my answer.
– harrymc
Feb 11 at 14:07
Sorry, but renaming the file will not help, it will be included in the sudoers anyway. Only deleting the file will fix the problem, as I wrote in my answer. Moreover, the name of the file causing the problem is actually 0pwfeedback.
– 1ng0
Feb 11 at 16:52
Thanks for the hint, but as I wrote, there is no pwfeedback in my
sudoers file.– 1ng0
Feb 11 at 13:30
Thanks for the hint, but as I wrote, there is no pwfeedback in my
sudoers file.– 1ng0
Feb 11 at 13:30
You missed out on the last paragraph in my answer.
– harrymc
Feb 11 at 14:07
You missed out on the last paragraph in my answer.
– harrymc
Feb 11 at 14:07
Sorry, but renaming the file will not help, it will be included in the sudoers anyway. Only deleting the file will fix the problem, as I wrote in my answer. Moreover, the name of the file causing the problem is actually 0pwfeedback.
– 1ng0
Feb 11 at 16:52
Sorry, but renaming the file will not help, it will be included in the sudoers anyway. Only deleting the file will fix the problem, as I wrote in my answer. Moreover, the name of the file causing the problem is actually 0pwfeedback.
– 1ng0
Feb 11 at 16:52
add a comment |
After some more research on files in the /etc/sudoers.d directory, I found the right answer here:
Linux Mint. How to set the terminal password to be invisible?
Is says:
"LinuxMint added the behavior in /etc/sudoers.d/0pwfeedback.
You could simply do like I did, delete the file as it contains only that adjustment:
sudo rm -rf /etc/sudoers.d/0pwfeedback"
Just renaming that file will not help.
answered Feb 11 at 13:36
1ng01ng0
13
add a comment |
After some more research on files in the /etc/sudoers.d directory, I found the right answer here:
Linux Mint. How to set the terminal password to be invisible?
Is says:
"LinuxMint added the behavior in /etc/sudoers.d/0pwfeedback.
You could simply do like I did, delete the file as it contains only that adjustment:
sudo rm -rf /etc/sudoers.d/0pwfeedback"
Just renaming that file will not help.
answered Feb 11 at 13:36
1ng01ng0
13
add a comment |
After some more research on files in the /etc/sudoers.d directory, I found the right answer here:
Linux Mint. How to set the terminal password to be invisible?
Is says:
"LinuxMint added the behavior in /etc/sudoers.d/0pwfeedback.
You could simply do like I did, delete the file as it contains only that adjustment:
sudo rm -rf /etc/sudoers.d/0pwfeedback"
Just renaming that file will not help.
answered Feb 11 at 13:36
1ng01ng0
13
After some more research on files in the /etc/sudoers.d directory, I found the right answer here:
Linux Mint. How to set the terminal password to be invisible?
Is says:
"LinuxMint added the behavior in /etc/sudoers.d/0pwfeedback.
You could simply do like I did, delete the file as it contains only that adjustment:
sudo rm -rf /etc/sudoers.d/0pwfeedback"
Just renaming that file will not help.
answered Feb 11 at 13:36
1ng01ng0
13
answered Feb 11 at 13:36
1ng01ng0
13
answered Feb 11 at 13:36
1ng01ng0
13
answered Feb 11 at 13:36
1ng01ng0
13
13
add a comment |
add a comment |
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%2f1404382%2fdisable-feedback-when-typing-password-at-a-sudo-prompt%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
