linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikel Bauer <mikel@bridgeband.net>
To: Keith Morse <kgmorse@mpcu.com>
Cc: "Kirkwood, David A" <DAVID.A.KIRKWOOD@saic.com>,
	"'linux-admin@vger.kernel.org '" <linux-admin@vger.kernel.org>
Subject: Re: changing password
Date: Wed, 30 Apr 2003 15:12:13 -0600	[thread overview]
Message-ID: <3EB03C2D.40003@bridgeband.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0304301350340.16158-100000@antares.mpcu.com>

Unfortunately, this will simply break your shadows.
The article on usenet refers to someone migrating from HPUX to RedHat.
The HPUX in question probably didn't have shadowed password, whereas 
redhat expects it.

pwconv takes a non shadowed password or group file, then creates the 
appropriate shadow. (pwunconv is the reverse).

The problem with your statement Keith is that if you delete the shadow 
file on a default redhat installation, you will have successfully 
deleted all of the passwords, and if you run pwconv on a standard redhat 
passwd file, you will basically have a copy of the passwd file, simply 
labelled shadow, minus the names, comments, shell and home.

This sounds more like a problem with either the passwd binary, or, if 
you are using it, PAM.

Unfortunately, I can offer no suggestions on what is really broken, or 
how to fix it.  I simply wanted to clear up the password issue.

-- 
Mikel Bauer
mikel@bridgeband.net

Keith Morse wrote:
> On Wed, 30 Apr 2003, Kirkwood, David A wrote:
> 
> 
>> I tries to change passwords on the system and get the following:
>>
>>Changing password for user root.
>>passwd: Authentication token manipulation error
>>
>>I shut the system down to single user and got the same.
>>
>>I am running RH7.3. I know I have changed the password before
>>and had the same problem, but don't remember what I did.
>>
>>All help is appreciated.
> 
> 
> In all the time I've administered Linux/Unix I've not seen this error. The 
> following may help.
> 
>>From a posting on UseNet via google:
> 
> http://www.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=200105032006.QAA06053%40kuznets.fas.harvard.edu&rnum=5&prev=/groups%3Fas_epq%3Dpasswd%253A%2520Authentication%2520token%2520manipulation%2520error%26safe%3Dimages%26ie%3DUTF-8%26oe%3DUTF-8%26lr%3D%26hl%3Den
> 
> 
>  Does the file /etc/shadow exhist?  The default install of Red
> Hat uses shadow passwords, and I think what may be happening in that
> qhen they try and change the password, there is no entry for the user in
> /etc/shadow, so pam has problems.  Backup /etc/shadow, and /etc/passwd.
> The delete /etc/shadow, and run pwconv to convert your password file to
> shadow passwords.  If this fixes the problem, you will also want to run
> grpconv.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 


  reply	other threads:[~2003-04-30 21:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30 17:14 changing password Kirkwood, David A
2003-04-30 20:52 ` Keith Morse
2003-04-30 21:12   ` Mikel Bauer [this message]
2003-04-30 21:11 ` Jeff Largent
  -- strict thread matches above, loose matches on Subject: below --
2003-05-01 14:01 Kirkwood, David A

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3EB03C2D.40003@bridgeband.net \
    --to=mikel@bridgeband.net \
    --cc=DAVID.A.KIRKWOOD@saic.com \
    --cc=kgmorse@mpcu.com \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).