CentOS 5 :: Account Password Changes Unexpectedly Once Every Few Days
May 5, 2009
I'm running 5.2, mostly updated. I've got a user account that is really only used by some clients (Polycom phones) to log into vsftpd. Once every few days or so, the password on the account changes to something other than what I've specified, and I can't figure out why. The other user accounts on the system don't seem to be affected, though none of the other accounts are used by/for vsftpd.
chage shows that the account password should never expire, so I don't think that's what's happening. I'm wondering if VSFTPD is just not playing nicely with PAM. Is there a way to explicitly prevent vsftp from changing a user password? I can't seem to find anything like this.I'm not sure if this makes any difference, but the system is clustered using heartbeat/drbd. The users are unique to each of the nodes in the cluster, though, so I don't think this should really have any effect.
We have one ftp server. Number of users are using it remotly. My requirement is that suppose any user is not connecting to the server using FTP for 15 days then account should get expired/locked automatically. Is it possible?
We have one ftp server. Number of users are using it remotly. My requirement is that suppose any user is not connecting to the server using FTP for 15 days then account should get expired/locked automatically. Is it possible?
When i try to login with AD credentials on Ubuntu 10.10 and the user has is password almost expire, the gdm hang and display the message "your password will expire in ... days"
If i login with any other user without that restriction, it works flawless. does anyone know what configuration file i need to change to bypass that problem.
am running centos5.3 on a virtual machine and was trying to do some basic hardening and part of it i had to modify the pam.d/system-auth file and from then i am getting a fatal error whenever i try to connect via ssh using putty i am not at all able to login the server with any of the accounts even root also.I am scared unknowingly did i lock the system???how to resolve this issue?
just started using Debian today and I would like to know how can I disable the user acount password, I am the only user on this computer so I would like it to boot strait into my account.
I'm still fairly new to Suse(and Linux) I have an account on my system that is locked when i run passwd -S accountname i get 'accountname lk' as the response. However when i try to unlock it using passwd -u accountname i get 'Cannot unlock the password for accountname!'.Any ideas on why i can't unlock the account?
After today's sudo upgrade on Karmic amd64, I am able to login only as root on my xubuntu system. Tried to change password on my user account but the result is the same.
I enter guest session and try to install an app. I am asked for a password, I try with mine (for my account) but it seems to be incorrect(logical). Well how can I find the password for the guest account???
I first started using Ubuntu and I liked the sudo facility because I didn't need to remember two passwords, so when I installed Debian I wrote the same password for the limited and the root account. Is this very bad for security? I mean can a program started from my regular account immediately become root or something?
I want to know how to change a password to an user account. Can someone give me the syntax on how to do this? I was using usermod but it's not working (usermod -p 123456 user1). Is there other way beside usermod? I am using RHEL5.
I am using Centos 5. I got one error unexpectedly after some configuration for rsync and folder settings. The error i am getting is "Serve Authorization directory (daemon/ServAuthDir) is set to /var/gdm but does not exist. Please correct the configuration and restart GDM." after rebooting.
I tried to resolve the issue by setting permission for folder /var/gdm to 755. but the problem is still not resolved.
Is there a way to login to an account with only the root password? Because I really need it the first unlock the computer next to me and second because I just want to know.
I suppose that my main Linux user account password serves as my SSH password as well. Is there a way I can modify this? As it turns out, I'd like to have a REALLY secure SSH password for obvious reasons, but a less secure local password, as it makes typing in passwords a heck of a lot easier on a machine. Is there a way I can change my account password in SSH without changing my Linux user password?
I created email account with commands "adduser -s /sbin/nologin test; passwd test";Is there any way to grant permission to user "test" to change his password by himself? My system is CentOS 4.4.
I have lost my password for my root and for my user account.
Code: Select alluser@debian:~$ su Password: su: Authentication failure user@debian:~$ su Password: su: Authentication failure user@debian:~$ su
I have just installed a gust debian 8 on debian 8 host in virtualbox, and when i wonted too login as su/root on the host there where no login possible, is there a way to regain the root password for the host?
Trying to set up my Yahoo account on KMail. After entering all the correct (as far as I know) server settings, ports, etc. and trying to check my mail from KMail, I get the following message.
Could not login to pop.mail.yahoo.com. The password may be wrong. The server said: "[SYS/PERM] pop not allowed for user."
The password is definitely right. What is going on?
When I first installed 9.04 (from scratch), I chose the option to have my entire account encrypted... I used the same password as my login password, and wrote down the key hash that it displayed for me just like instructed... everything was working terrific...Well, yesterday, I wanted to change my account password. I changed my account password, and it took effect immediately (I tested it by using "sudo -s" to see if I could elevate to root from the terminal... worked just fine). Being satisfied with my new password, I shut my computer down...
The next time I started it up and tried to log in to my account, it I put in my username and password and pressed enter, and it accepted it just fine, and started to boot to my desktop... it then immediately prompted me with something about "your session lasted less than 10 seconds, try starting in failsafe mode" or something along those lines, and immediately booted me out and back to the gdm login screen... I thought it was just a glitch so I tried again... same thing... gave me the "less than 10 seconds" prompt and booted me back to the gdm...
I thought maybe my filesystem became corrupted, but I didn't give up... I attempted to login to my fiancee's account, and it worked just fine! Using her account, I was able to quickly and safely boot into her desktop environment with no errors...I opened a terminal and used the "su" command to access my account... When I did this, it gave me some kind of error and told me to run ecryptfs (can't remember exactly which command... now). I ran ecryptfs and put in my NEW password... it told me that the passphrase was incorrect. So just out of curiosity, I ran it again, and this time put in my OLD passphrase, and it worked immediately! At this point, I realized that my gdm login password got changed, but my ecryptfs passphrase did not, and the two were not matching up (I assume that on login, gdm passes this password on to ecryptfs, and that when the two did not match up, it was booting me out with the whole "session lasted less than 10 seconds" prompt...)...
So what I did at this point was, while logged into my girlfriend's account, I "su"'d into my account, and used the passwd command to change my password back to my OLD password... once the password was changed back successfully, I restarted my computer and tried to log into my account from the gdm... worked perfectly this time with the old (original) password...When you change your session password, shouldn't it automatically change the encyrption password to match? Or at the very least, warn you that if your account is encrypted, you must take further steps to make these two passphrases match? Also, what command would I use to change my "ecryptfs" password to manually match my session password?
I'm trying to configure a process triggered by an SVN post-commit hook which will log into a different host and carry out an SVN update on a file path on that host before exiting. An earlier attempt mounted the remote filepath on the SVN host using sshfs and performed the update locally. This worked but it was incredibly slow (minutes to complete an SVN update).
So, Plan B was to set-up a passwordless login for the user the script runs as and then use pam-script to script a checkout from a repository using the same credentials. The problem is, passwordless SSH login using private/public keys appears to bypass the PAM authentication system or at least interact with it in a way that no environment variables (including the SSH user's name and pass) are resolved by the authentication script being used by pam-script.
I've tested the pam-script behaviour for normal log-ins and it exposes these variables fine. This leaves me in a Catch-22 with trying to script access on one host to perform actions on another while avoiding user/pass prompts or the need to store plaintext passwords on the remote host.
Anyone know if there's a way to resolve a user account password via PAM when using passwordless SSH or, another approach I could take to perform scripted tasks on the remote system requiring authentication? Ideally without storing the passwords on the remote system (at least in unencrypted form).
I remember my password very well and have no need of password recovery. Everywhere I look it's how to recover and I don't want that. The kind where you boot into root recovery console to change the password.
