I'm wondering about the pros and cons of simplifying the default chat -
maybe something like:
*password* %n\n *password* %n\n *success*
This should work on my system as well. I'm not sure about the system
from the "Example 3.4. 130 User Network with tdbsam [globals] Section",
since the final "success" condition may or may not report "success"
after the password is reported changed.
Anyway, a simpler default dialogue would make the chat more immune to
differences between systems, so things like "retype" versus "re-enter"
wouldn't come into play.
Ben Walton wrote:
Yes, I just verified this on my setup. I've never had luck in the
past, but I must have had a non-working password chat at those times
(quite some time ago now). Apologies for misleading anyone.
I have a 'unique' setup for my user accounts, so my little script
will still be useful for certain purposes here, but I can now allow
normal password changes.
Thanks Eric & Simo. -Ben
On Thu, 2006-03-30 at 15:04 -0500, Eric J. Feldhusen wrote:
> On a RHEL4, with Samba 3.0.10, I have the following password
> options below. I just tested and with a WinXP Pro client, I did
> the ctrl-alt-delete and changed my password. Once I did that, I
> ssh'ed into the box and it used my new password.
>
>
> [global] encrypt passwords = yes
>
> null passwords = yes
>
> obey pam restrictions = yes
>
> passwd chat = *New*UNIX*password*
> %n\n*ReType*new*UNIX*password*%n\n
> *passwd:*all*authentication*tokens*update d*successfully*
>
> passwd program = /usr/bin/passwd %u
>
> unix password sync = Yes
>
>
> Ben Walton wrote:
>
>> A note on the password sync issue. Someone more knowledgeable
>> correct me if I'm wrong.
>>
> -- Eric Feldhusen System Administrator http://www.remc1.org
> [EMAIL PROTECTED] PO Box 270 (906) 482-4520 x239 809
> Hecla St (906) 482-5031 fax Hancock, MI 49930 (906) 370
> 6202 mobile
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
