Re: problem after patching openssh 3.7.1p2
From: Vahid (NOSPAM-sunman_at_ureach.com)
Date: 11/27/03
- Previous message: Mike: "Re: Plain & Simple . . ."
- In reply to: Darren Tucker: "Re: problem after patching openssh 3.7.1p2"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 27 Nov 2003 20:05:05 GMT
Darren Tucker wrote:
> In article <64b3dda3.0311260722.254d3b25@posting.google.com>,
> Vahid <sunman@ureach.com> wrote:
>
>>Let me explain the steps I am taking to compile openssh, before
>>complaining about the errors:
>>- I untar the snapshot ...
>>cd openssh
>>GNUpatch -p1 < openssh-3.7.1p2-pwexp24.patch # applies ok
>>GNUpatch -p1 < openssh-3.7.1p2-pwexp25.patch # need to say patch
>>anyway
>>GNUpatch -p1 < openssh-3.7.1p2-pwexp26.patch # need to say patch
>>anyway
>>
>>cd ..; tar openssh.tar openssh # to take to other platforms...
>>cd openssh
>>./configure
>>
>>Am I doing anything wrong or out of order?
>
>
> You only need to apply one of those patches (you probably want 26).
>
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
with no compilation problem but still accounts with "passwd -f" can not
set password.
My main target platform is Solaris 8, Should I just use PAM? Would that
fix my problems or create more?
Thank you,
- Previous message: Mike: "Re: Plain & Simple . . ."
- In reply to: Darren Tucker: "Re: problem after patching openssh 3.7.1p2"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|