Re: OpenSSH b0rked (was RE: Problems with IPFW patch)
From: Kris Kennaway (kris@FreeBSD.ORG)
Date: 01/25/01
- Next message: Kris Kennaway: "Re: Problems with IPFW patch"
- Previous message: Scott Raymond: "OpenSSH b0rked (was RE: Problems with IPFW patch)"
- In reply to: Scott Raymond: "OpenSSH b0rked (was RE: Problems with IPFW patch)"
- Next in thread: Scott Hilton: "RE: OpenSSH b0rked (was RE: Problems with IPFW patch)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 24 Jan 2001 18:34:57 -0800 From: Kris Kennaway <kris@FreeBSD.ORG> To: Scott Raymond <scott@link-net.com>
On Wed, Jan 24, 2001 at 04:55:38PM -0800, Scott Raymond wrote:
> Yeah, now if I could just figure out what was wrong with the openssh
> implementation in the core system. Openssh (ports tree version) has an
> annoying install sequence - you can't define where it gets installed, so
> the files get installed to the hard-coded directory tree /usr/local.
> The non-working core system one normally installs sshd to /usr/sbin and
> the config files to /etc/ssh.
Perhaps if you posted an actual error..? :)
Dusting off my magic crystal ball, I predict you aren't using the
official upgrade procedure which involves running mergemaster (and
haven't read the reminder notice in /usr/src/UPDATING), and have an
out of date /etc/pam.conf.
Kris
-- NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message
- application/pgp-signature attachment: stored
- Next message: Kris Kennaway: "Re: Problems with IPFW patch"
- Previous message: Scott Raymond: "OpenSSH b0rked (was RE: Problems with IPFW patch)"
- In reply to: Scott Raymond: "OpenSSH b0rked (was RE: Problems with IPFW patch)"
- Next in thread: Scott Hilton: "RE: OpenSSH b0rked (was RE: Problems with IPFW patch)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|