From nobody@FreeBSD.org  Tue Feb  6 21:02:51 2001
Return-Path: <nobody@FreeBSD.org>
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id 9223037B401
	for <freebsd-gnats-submit@FreeBSD.org>; Tue,  6 Feb 2001 21:02:51 -0800 (PST)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f1752p850221;
	Tue, 6 Feb 2001 21:02:51 -0800 (PST)
	(envelope-from nobody)
Message-Id: <200102070502.f1752p850221@freefall.freebsd.org>
Date: Tue, 6 Feb 2001 21:02:51 -0800 (PST)
From: rick@pacwestconsulting.com
To: freebsd-gnats-submit@FreeBSD.org
Subject: ssh modules not  loading
X-Send-Pr-Version: www-1.0

>Number:         24918
>Category:       misc
>Synopsis:       ssh modules not  loading
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Feb 06 21:10:01 PST 2001
>Closed-Date:    Wed Feb 7 00:06:52 PST 2001
>Last-Modified:  Wed Feb  7 03:10:04 PST 2001
>Originator:     Rick Barker
>Release:        4.2 Stable
>Organization:
Pacific West Consulting
>Environment:
FreeBSD orca.pacwestconsulting.com 4.2-STABLE FreeBSD 4.2-STABLE #1: Mon Feb  5 22:10:09 PST 2001     root@orca.pacwestconsulting.com:/usr/src/sys/compile/pacwest  i386
>Description:
Unable to connect using SecureCRT using ssh2
The following error is writen to the console

sshd[336]: no modules loaded for 'sshd' service
sshd[336]: fatal: PAM session setup failed[6]: Permission Denied
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: kris 
State-Changed-When: Wed Feb 7 00:06:52 PST 2001 
State-Changed-Why:  
Submitter has out of date /etc 

http://www.freebsd.org/cgi/query-pr.cgi?pr=24918 

From: Kris Kennaway <kris@obsecurity.org>
To: rick@pacwestconsulting.com
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: misc/24918: ssh modules not  loading
Date: Wed, 07 Feb 2001 00:06:33 -0800

 --wRRV7LY7NUeQGEoC
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Tue, Feb 06, 2001 at 09:02:51PM -0800, rick@pacwestconsulting.com wrote:
 
 > Unable to connect using SecureCRT using ssh2
 > The following error is writen to the console
 >=20
 > sshd[336]: no modules loaded for 'sshd' service
 > sshd[336]: fatal: PAM session setup failed[6]: Permission Denied
 
 Follow the upgrade instructions in the handbook and run mergemaster
 after the conclusion of every installed world.
 
 Kris
 
 --wRRV7LY7NUeQGEoC
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.4 (FreeBSD)
 Comment: For info see http://www.gnupg.org
 
 iD8DBQE6gQIIWry0BWjoQKURAuAkAKDX4Fn/TtkEoTHslO0mvmY4xRnNtgCfc8Q4
 tV5IRZBWlgVXYFPBk6hnrFY=
 =rfZA
 -----END PGP SIGNATURE-----
 
 --wRRV7LY7NUeQGEoC--
 

From: Peter Pentchev <roam@orbitel.bg>
To: rick@pacwestconsulting.com
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: misc/24918: ssh modules not  loading
Date: Wed, 7 Feb 2001 12:57:11 +0200

 On Tue, Feb 06, 2001 at 09:02:51PM -0800, rick@pacwestconsulting.com wrote:
 > 
 > >Number:         24918
 > >Category:       misc
 > >Synopsis:       ssh modules not  loading
 > >Originator:     Rick Barker
 > >Release:        4.2 Stable
 > >Organization:
 > Pacific West Consulting
 > >Environment:
 > FreeBSD orca.pacwestconsulting.com 4.2-STABLE FreeBSD 4.2-STABLE #1: Mon Feb  5 22:10:09 PST 2001     root@orca.pacwestconsulting.com:/usr/src/sys/compile/pacwest  i386
 > >Description:
 > Unable to connect using SecureCRT using ssh2
 > The following error is writen to the console
 > 
 > sshd[336]: no modules loaded for 'sshd' service
 > sshd[336]: fatal: PAM session setup failed[6]: Permission Denied
 
 My guess would be that you updated your src tree and built world after
 OpenSSH 2.3.0 was brought into the tree.
 
 Did you also follow the instructions in /usr/src/UPDATING and run
 mergemaster (as you should before or after EVERY world update)?
 
 If you did not explicitly run mergemaster, did you add the relevant
 lines to /etc/pam.conf, again as stated in /usr/src/UPDATING?
 
 G'luck,
 Peter
 
 -- 
 I am the meaning of this sentence.
 
>Unformatted:
