Hot answers tagged password
There is timestamp_timeout option in your /etc/sudoers. You can set up this option to number of minutes. After that time it will ask for password again. More info in man sudoers. And make sure you edit your sudoers file using visudo, which checks your syntax and which will not leave you with wrong configuration and inaccessible sudo.
There is a timestamp_timeout option in your /etc/sudoers... Example: to get password remembered for 5 hours Defaults timestamp_timeout=300
I'm not sure why you would want to do that. If you're concerned about security, if someone discovers your password on 1 July, they'll know it on 31 July or 15 September... To answer your question, if you want to ensure that the password update is done either at a scheduled time or when the system restarts, you want to install anacron. It can do periodic ...
sudo su asks for the user's password, the user has to be in the sudo/adm/admin/wheel group (depening on flavour of the OS) to be able to execute sudo. The root password will be prompted when using su alone. Check the settings in /etc/sudoers file to see why you are not being asked for a password while using sudo. Most likely the time-out is set to a few ...
Don't use password authentication. Use ssh keypairs. Karthik@A $: ssh-keygen #keep the passphrase empty Karthik@A $: ssh-copy-id B #enter your B password #^ this will copy your public key to Karthik@B:.ssh/authorized_keys From then on, you should be able to ssh from A to B (and by extension, scp from A to B) without a password.
Running this command without SSH keys should prompt you for a password. I am using something similar and don't have any problems. Most probably you are having problems connecting to the ssh server. Make sure You have access to the server. You can run traceroute your.server.ip.address to see if you can connect to it. Make sure you have the ssh server up ...
You asked how to create one, but just in case you want one: https://forums.hak5.org/index.php?/topic/29308-13gb-44gb-compressed-wpa-wpa2-word-list-982963904-words/ As for creating one, consider checking out a program called crunch (wordlist generator).
Reading between the lines, what you want to configure is two-factor authentication. This will require an additional "piece of information" in addition to the password for the user to log in. There are a multitude of ways of implementing it, but a few popular options are: The open source Google Authenticator. Using a third party product like YubiKey - see ...
I read with Wayland there comes the infrastructure to prohibit it, but now it's still a problem. Just see xinput test-xi2 The first article I read about the problem: http://theinvisiblethings.blogspot.de/2011/04/linux-security-circus-on-gui-isolation.html Further and deeper discussion: http://lwn.net/Articles/517375/
I don't think it's a bad idea to harden your system by protecting accounts as good as possible as you can. In many situations it will introduce extra hurdles during authentication, but if you're willing to cope with that it's all fine. An important thing to take into account, though, is the risk of actually introducing more flaws by increasing the complexity ...
You have to check man passwd: If the encrypted password is set to an asterisk (*), the user will be unable to login using login(1), but may still login using rlogin(1), run existing processes and initiate new ones through rsh(1), cron(8), at(1), or mail filters, etc. Trying to lock an account by simply changing the ...
This means that it is a disabled login. You cannot login with that username. It is a user that is used for running services. Check https://en.wikipedia.org/wiki/Passwd#Password_file
Use chage -l pooja, where pooja is your login name. This command is available also to the nonprivileged user. If you're root, you can also use passwd -S pooja.
Open KWalletManager (/usr/bin/kwalletmanager) in KDE, go to Contents / Form Data / Maps, select the correct id, check Show Values box. Works for me. If you can't find it this way: save your login page to a HTML file, place it on a localhost webserver with PHP/CGI support, trick your resolver via /etc/hosts to call local page instead of the original, write a ...
You can also use password less connections, just use public/private key and you are ready to go. Using lftp client you can establish connections giving username/password as a parameter in the command line lftp sftp://sftp_server -uuser,password
The list of groups a user belongs to is stored in /etc/group When you add a user to group /etc/group is updated. The /etc/passwd file doesn't tell you which users belong to which groups. It only has the group id of the user's default group. The groups command returns info from /etc/group
A quick search turned up Two Factor SSH Setup which is a simple walkthrough of the steps required for setup.
If you can run the command as root, you can force the change to be accepted. Example: # sudo passwd myusername Changing password for user myusername. New password: Retype new password: passwd: all authentication tokens updated successfully.
Only top voted, non community-wiki answers of a minimum length are eligible