| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 9052.1 | one idea | GERUND::WOLFE | I'm going to huff, and puff, and blow your house down | Thu Mar 06 1997 12:20 | 6 |
| Did you use the same password in all your tests? I'm pretty sure
I saw this problem when I had a password longer than 8 characters.
passwd silenty truncates the password to 8 but yppasswd didn't
and gave this error.
pete
|
| 9052.2 | it works with V3.2c, why not on V4.0 ? | MUNICH::CUZUM | | Fri Mar 07 1997 03:49 | 6 |
| Hi, Pete,
I didn't check for password-length, but if it's the password, would it
work from V3.2c slaves but not from V4.0 slaves?
Corina
|
| 9052.3 | | GERUND::WOLFE | I'm going to huff, and puff, and blow your house down | Fri Mar 07 1997 13:26 | 5 |
| If it was the exact same (long) password in all cases, then yes, I would
expect it to fail for 3.2 and 4.0. That's why I asked if you
kept it the same across all the tests.
pete
|
| 9052.4 | doesn't work with short password | MUNICH::CUZUM | | Mon Mar 17 1997 03:13 | 7 |
| I let the customer test it with a 5-character password and again it
didn't work. Any other ideas please?
Thanks,
Corina
|
| 9052.5 | | NETRIX::"[email protected]" | Ann Majeske | Mon Mar 17 1997 12:03 | 7 |
| If you use the -S flag, make sure that the slave server name is entered
correcly on the master server NIS args, and the master server name is
entered correctly on the slave server NIS args (in /etc/rc.config).
Did you follow the instructions in section 7.4.1 - Adding an NIS Slave
Server to a Domain, in the V4.0 Network Administration Guide?
[Posted by WWW Notes gateway]
|
| 9052.6 | yppasswd still doesn't work | MUNICH::CUZUM | | Mon Mar 24 1997 10:33 | 16 |
| I let the customer reinstall everything according to the manual. He
send me a protocoll he made with the script-command and everything
looked ok. I found out that his /usr/bin/yppasswd had no suid-bit. I
let him set the suid-bit on /usr/bin/yppasswd to have the correct
permissions, but again it didn't work.
We checkt all entrys for the master and slave system but found no
mistake.
I even managed to install here a V4.0 Slave Server, but couldn't
reproduce his problem. So it isn't a bug. Seems to be a configuration
problem. Now I ran out of ideas, I don't know what else I could check
and I'm desperate!!!!
Please, has anyone any idea?
Desperately,
Corina
|
| 9052.7 | root can do yppasswd on the slave server | MUNICH::CUZUM | | Mon Mar 24 1997 10:45 | 7 |
| I forgot to say, that the customer let me know, he can change passwords
for users an the slave server, when he logs in as root. But it should
also wotk that users change their own passwords.
Still desperately,
Corina
|
| 9052.8 | | NETRIX::"[email protected]" | Ann Majeske | Tue Mar 25 1997 11:47 | 17 |
| The yppasswd command does not need setuid to work. The protections/ownership
of yppasswd should look something like:
% ls -als /usr/bin/yppasswd
-rwxr-xr-x 1 bin bin 24576 Nov 15 22:10 /usr/bin/yppasswd
From your original description, it looks like the customer is never getting
the prompt to enter the old password. I looked at that section of source
code, and if it is true that your customer is never getting the prompt for
the old password, the line of code that is "failing" is:
if((fi = fopen("/dev/tty", "r+")) == NULL)
Most likely this is an indication of a problem with the ownership/permissions
of the terminal (or pseudoterminal) the customer is using to try to change
the password. Also, note that you are required to use an interactive terminal
to change the password, you can't do it from a script.
[Posted by WWW Notes gateway]
|