similar to: 6253934 passwd and pwconv are crashing with wrong entry in /etc/shadow

If shadow passwords are already in use, and new entries are appended to /etc/passwd that include password hashes, is it still possible to use pwconv to generate /etc/shadow entries for just the few newly appended accounts? Regards, Eugene

I''m working on an issue we noticed in openstack where setting the root password on a CentOS 6 image through the XenAPI would corrupt the guest image''s /etc/shadow file. 1. set the root password through XenAPI 2. log in to the account 3. `passwd` -- you should get an error. To fix you can `rm /etc/shadow; pwconv` I''ve tested against an Ubuntu XCP image and everything

Hello All, We have been successfully using PAM_LDAP authentication with OpenSSH-3.6 on our HP-UX 11.11. When OpenSSH-3.7.1p2 is installed [with Darrens' password expiry patch 26], and when Shadow password bundle is installed on the system, our ssh authentication failed. Even, when the source is compiled without Darren's patch, the same bahaviour is seen and there is no success. When

Author: basabi Repository: /hg/zfs-crypto/gate Revision: 4bb3638905e4a1eb6ee0228d46cc603b32dfef22 Log message: 6408445 logadm rotates regardless with -s 2g Files: update: usr/src/cmd/logadm/fn.c update: usr/src/cmd/logadm/fn.h update: usr/src/cmd/logadm/main.c update: usr/src/cmd/logadm/opts.c update: usr/src/cmd/logadm/opts.h

Hi Folks, I need to use Shadow Passwords or point Samba to a password file other then /etc/passwd. Do I need to be running 1.9.17? If you could please respond to me privately, I'll post a summary of responses to the list. Thank You Pam Buffington pamc@cc.gatech.edu

Hello, This patch fix order of checking password in systems that contains /etc/shadow file (Linux for example). The order is exactly like in linux-shadow-password package. First is checked /etc/passwd but if password field contains "x" then password is read from /etc/shadow instead. Best regards, Krzysztof Ol?dzki -------------- next part -------------- A non-text attachment was

How can i configure samba to use /etc/passwd and /etc/shadow for the samba passwords? I dont want to use smbpasswd for samba and would like it to just get its passwords from unix OS. Im running solaris8 and samba 3. thanks! ____________________________________ This e-mail message is for the sole use of the intended recipient(s) and may contain proprietary, confidential and/or privileged

We've been running Samba2.2.x and relying on the underlying Solaris user authentication (/etc/passwd /etc/shadow). For historical reasons, we've allowed plaintext passwords. Now as we've upgraded to Samba 3.0.3. we would like to continue this method of authentication (at least until we can implement ldap). The docs are sketchy at best (you can use plaintext authentication, etc.), but

Fellow list members, I recently tried to add a user to a little used server that hadn't see a change in users for quite a while. When I use system-config-users I get an error alert that says - The user database cannot be read. This problem is most likely caused by a mismatch in /etc/passwd and /etc/shadow. The program will exit now. I awk'ed out the user ID's and ran diff.

Hi Guys, I am new to puppet and trying to figure out what is the best way to manage a password for a specific user in the /etc/shadow file. Most of my users are being authenticated to kerberos but there is a need to set a local password for this one account. What would be the best method to do this via puppet? I have built my own rpm''s in the past using the chpasswd command but

Hello All, I''m new to puppet, and I''d like to know: Is there a formal best practices guide for syncing { /etc/passwd, shadow, group, hosts} across clients from the master? For instance; is it a better practice to make a hard link to these files and share the link, as opposed to just sharing the files directly via a target in fileserver.conf? Inquiring minds want to know...

Greetings everyone, I have a question about the smbpasswd encrypted database and /etc/passwd -- why does the passdb backend require an entry in /etc/passwd? Is it possible to create samba encrypted users without a /etc/passwd entry? I have a samba PDC setup that is mainly just a login server, then a separate server for $HOME's. I have all of my PAM configs setup to remotely authenticate

prepping to teach a 5-day CompTIA linux+ course next week with CompTIA-supplied courseware and, given that it was my choice, i chose to set up the classroom with centos 7.4 on all the student systems since i assume most students are there to learn sysadmin and that's the most likely platform they'll have when they get back to work. also, most students are taking this course to prep for the

From: Feizhou > Yes, I was wondering whether you were trying to say that Samba > could do the extra cruff MS threw into their > Kerberos/LDAP/DNS thingamich. ? Microsoft uses SRV records in DNS. That was actually a _good_ move. Now their DNS-integrated ADS is another story. Although I do have to say the current, split dhcpd, named, nmbd strategy in the open source world is rather

From: Feizhou > I know what a Kerberos authentication system is. > You mean a core component in Samba 3.0's functionality as an ADS client. You're still artificially limiting your understanding. Kerberos (with the MS extensions in the case of 200x/XP) is how objects authenticate each other and grant tickets for access in a Kerberos realm. Samba can use Kerberos how it sees fit.

Hi! here is the problem , i have local users some have shadow password, some not, so i must create two auth one to login via shadow , and one via passwd so here is my config file (stripped comments): protocols = imap imaps pop3 pop3s imap_listen = 192.168.0.2 pop3_listen = 192.168.0.2 imaps_listen = 192.168.0.2 pop3s_listen = 192.168.0.2 login = imap login = pop3 auth = default auth_mechanisms

I'm trying to get authentication to work without PAM and just use the standard shadow and passwd files. auth default { userdb passwd { } passdb shadow { } } This seems to be valid code to use /etc/passwd and /etc/shadow. My linux distro is using Salted MD5. Though Dovecot keeps telling me that authentication failed. It doesn't give me any error messages regarding the config. Any

is it possible to cut and paste linux shadow file passwd hashes to smbpasswd file?

I'm using an alternate password/shadow combo to authenticate IMAP users and I can't seen to get it working... I'm using: passdb shadow { args = /etc/dovecot/shadow } Can somebody please give me some hints on how to get this to work.... Thanks JB

From: Dag Wieers > Bryan, and you're still belittling people in discussions and get into long > arguments as a result. Pretty please stop doing that. I apologize for any belittling. It is not my intent, but I do see a repeat theme. People thing in single products/projects, not breaking down things into their multiple technologies. That's all I meant by "artificially