09-01-2017
Show Asterisks when changing Password
Note: **Showing Asterisks when using SUDO is not what I am looking for. That method is well documented**
Short Description: We have a requirement where users want to see that they are typing a password when logging into a RedHat box or when they are changing their password -- instead of seeing nothing.
Reason for request: I have Windows users who use an application where I configured Windbind to connect to our Active Directory environment for account authentication. After x number of days, users are required to change their AD password via a Unix interface. *nix default behavior as we know, is to not show asterisks/anything when typing a password (for security or 'dev folk never got around to changing the code to change this behaviour' reasons). Whatever the case, I have been asked if there was a way to allow for Asterisks to be shown when users are logging in or changing their password. Is there a configuration change anybody is aware of, or a commercial product that will do this?
I have found many - many posts to do it when using SUDO, but this will not accomplish what I need to do.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
SCO OpenServer 5.05
Has anyone ever received this error when attempting to
change/assign a user password?
#ypasswd
=======================================
yppasswd: (host name) is not running yppasswd daemon
Password request denied.
Reason: Remote password change request denied.... (2 Replies)
Discussion started by: gseyforth
2 Replies
2. Solaris
Hi
Someone logged on the system with a Normal user and changed the password , for this user , how can i know ? who changed the password from which terminal ?
regards
Georges (5 Replies)
Discussion started by: itsgeorge
5 Replies
3. UNIX for Dummies Questions & Answers
Hello
im trying to change the user password with passwd
but when I enter the password it gives me this msg:
passwd: Password too short - must be at least 6 characters.
BUT the thing is that the initial password was 4 letters why now it asking for 6 ?
tnx (2 Replies)
Discussion started by: umen
2 Replies
4. AIX
I have 02 servers:
- Linux RHEL AS 3 (server1)
- AIX 5.2 (server2)
Running the command rsh server2 passwd derje from the server1 to change derje user password on server2, give me this error:
3004-709 Error while changing the password for "derje"
Can somebody help me ? (0 Replies)
Discussion started by: mayge
0 Replies
5. HP-UX
I have two unix system A and B with same configuration.
I can use remsh from A system login to B system as root, but when I want to change the root password of B system, it ask me the old password, but i forgot it.
However, is it possible to change the B system root password? :(
Thanks a lot (3 Replies)
Discussion started by: zetadhell
3 Replies
6. Solaris
Hello,
I want to know the reason behing the scene why some systems have hashed password in /etc/shadow file as "x" not the alienoid language like A1Dksxi3kaA.. (13 characters)
As far as I understand, etc/password will show password as "x" and move all hashed password to etc/shadow.... (8 Replies)
Discussion started by: Smith
8 Replies
7. Solaris
Friends
I want to know whether i can change the password of a user logged in thru NIS from a client machine after stopping the YP services in NIS server.
Note - The Slave server is up and running.
I tried doing this. But i got the reply "Permission Denied".
I stopped the YP services in... (7 Replies)
Discussion started by: efunds
7 Replies
8. UNIX for Advanced & Expert Users
Is there any way I can change the prompt which asks for the password on a UNIX system? e.g. When I login using Telnet instead of "Password" I should get "Correct Password".
Thanks,
Vineet (3 Replies)
Discussion started by: vineetd
3 Replies
9. Shell Programming and Scripting
Hi all
Im trying to learn the basics of bash and am struggling with some file manipulation. I am trying to run a script that once you have logged in allows you to change your password which is held (along with the corresponding username) in a different file called usernames. When i try to run my... (2 Replies)
Discussion started by: somersetdan
2 Replies
10. AIX
I want to change the root password on an AIX box. What is the best method to do this so i do not get myself locked out. When I do i search the results come up for resetting the password if you are locked out.
Thanks (5 Replies)
Discussion started by: fierfek
5 Replies
LEARN ABOUT LINUX
sudo_root
sudo_root(8) System Manager's Manual sudo_root(8)
NAME
sudo_root - How to run administrative commands
SYNOPSIS
sudo command
sudo -i
INTRODUCTION
By default, the password for the user "root" (the system administrator) is locked. This means you cannot login as root or use su. Instead,
the installer will set up sudo to allow the user that is created during install to run all administrative commands.
This means that in the terminal you can use sudo for commands that require root privileges. All programs in the menu will use a graphical
sudo to prompt for a password. When sudo asks for a password, it needs your password, this means that a root password is not needed.
To run a command which requires root privileges in a terminal, simply prepend sudo in front of it. To get an interactive root shell, use
sudo -i.
ALLOWING OTHER USERS TO RUN SUDO
By default, only the user who installed the system is permitted to run sudo. To add more administrators, i. e. users who can run sudo, you
have to add these users to the group 'admin' by doing one of the following steps:
* In a shell, do
sudo adduser username admin
* Use the graphical "Users & Groups" program in the "System settings" menu to add the new user to the admin group.
BENEFITS OF USING SUDO
The benefits of leaving root disabled by default include the following:
* Users do not have to remember an extra password, which they are likely to forget.
* The installer is able to ask fewer questions.
* It avoids the "I can do anything" interactive login by default - you will be prompted for a password before major changes can happen,
which should make you think about the consequences of what you are doing.
* Sudo adds a log entry of the command(s) run (in /var/log/auth.log).
* Every attacker trying to brute-force their way into your box will know it has an account named root and will try that first. What they do
not know is what the usernames of your other users are.
* Allows easy transfer for admin rights, in a short term or long term period, by adding and removing users from the admin group, while not
compromising the root account.
* sudo can be set up with a much more fine-grained security policy.
* On systems with more than one administrator using sudo avoids sharing a password amongst them.
DOWNSIDES OF USING SUDO
Although for desktops the benefits of using sudo are great, there are possible issues which need to be noted:
* Redirecting the output of commands run with sudo can be confusing at first. For instance consider
sudo ls > /root/somefile
will not work since it is the shell that tries to write to that file. You can use
ls | sudo tee /root/somefile
to get the behaviour you want.
* In a lot of office environments the ONLY local user on a system is root. All other users are imported using NSS techniques such as
nss-ldap. To setup a workstation, or fix it, in the case of a network failure where nss-ldap is broken, root is required. This tends to
leave the system unusable. An extra local user, or an enabled root password is needed here.
GOING BACK TO A TRADITIONAL ROOT ACCOUNT
This is not recommended!
To enable the root account (i.e. set a password) use:
sudo passwd root
Afterwards, edit the sudo configuration with sudo visudo and comment out the line
%admin ALL=(ALL) ALL
to disable sudo access to members of the admin group.
SEE ALSO
sudo(8), https://wiki.ubuntu.com/RootSudo
February 8, 2006 sudo_root(8)