Re: OpenSSH-2.9.X and GCC-2.95.3
From: Jon Abrams (jabrams@ideasculptors.net)Date: 10/23/01
- Previous message: Darren Moffat: "Re: chroot and BIND"
- Maybe in reply to: Geoff Collis: "OpenSSH-2.9.X and GCC-2.95.3"
- Next in thread: Geoff Collis: "RE: OpenSSH-2.9.X and GCC-2.95.3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 23 Oct 2001 20:45:35 -0000 Message-ID: <20011023204535.21218.qmail@mail.securityfocus.com> From: Jon Abrams <jabrams@ideasculptors.net> To: focus-sun@securityfocus.com Subject: Re: OpenSSH-2.9.X and GCC-2.95.3('binary' encoding is not supported, stored as-is) Mailer: SecurityFocus
In-Reply-To: <3C33BA4DEAB2D511A16900500488E66111D546@mail.vendorhub.com>
>Has anyone else run into similar problems?
>
>- Geoff Collis
>
I found via the comp.security.ssh newsgroup that you
need to add the parameter --with-cflags="-
DPAM_TTY_KLUDGE" when running configure to get
around PAM bugs. This fixed my problems.
- Jon Abrams
- Previous message: Darren Moffat: "Re: chroot and BIND"
- Maybe in reply to: Geoff Collis: "OpenSSH-2.9.X and GCC-2.95.3"
- Next in thread: Geoff Collis: "RE: OpenSSH-2.9.X and GCC-2.95.3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|