Re: problem after patching openssh 3.7.1p2
From: Darren Tucker (dtucker_at_dodgy.net.au)
Date: 12/01/03
- Next message: Darren Tucker: "Re: compressed connection problem on 3.7.1p2"
- Previous message: Bill Heafey: "Logging failed login attempts?"
- Next in thread: Vahid: "Re: problem after patching openssh 3.7.1p2"
- Reply: Vahid: "Re: problem after patching openssh 3.7.1p2"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 01 Dec 2003 04:56:14 GMT
In article <3FC659D6.6000406@ureach.com>,
Vahid <NOSPAM-sunman@ureach.com> wrote:
>I applied each patch, one at a time to the new untared source but I get
>PASSWD_PROGRAM_PATH error every time, then I did '#define
>PASSWD_PROGRAM_PATH "/usr/passwd"' in the config file and recompiled
You probably mean "/usr/bin/passwd" ?
>with no compilation problem but still accounts with "passwd -f" can not
>set password.
I don't see how you can be getting the results you're getting. Solaris
8 is one of my test platforms and I'm pretty sure it works. Would you
please do the steps exactly as described at:
http://www.zip.com.au/~dtucker/openssh/
(ie the part starting with "The basic procedure is") and mail me the
entire output at the email address in the footer of this message?
>My main target platform is Solaris 8, Should I just use PAM? Would that
>fix my problems or create more?
The 3.7.1p2 out-of-the-box code won't do what you want (I don't think so,
anyway).
--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.
- Next message: Darren Tucker: "Re: compressed connection problem on 3.7.1p2"
- Previous message: Bill Heafey: "Logging failed login attempts?"
- Next in thread: Vahid: "Re: problem after patching openssh 3.7.1p2"
- Reply: Vahid: "Re: problem after patching openssh 3.7.1p2"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|