From owner-freebsd-security Fri Sep 11 10:30:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01473 for freebsd-security-outgoing; Fri, 11 Sep 1998 10:30:46 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from colin.muc.de (colin.muc.de [193.174.4.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA01453 for ; Fri, 11 Sep 1998 10:30:37 -0700 (PDT) (envelope-from lutz@muc.de) Received: from tavari.muc.de ([193.174.4.22]) by colin.muc.de with SMTP id <140576-1>; Fri, 11 Sep 1998 18:02:03 +0200 Received: (from daemon@localhost) by tavari.muc.de (8.8.8/8.8.7) id SAA08916; Fri, 11 Sep 1998 18:00:50 +0200 (CEST) Received: from ripley(192.168.42.202) by morranon via smap (V2.1) id xma008914; Fri, 11 Sep 98 18:00:43 +0200 From: "Lutz Albers" To: "Graphic Rezidew" , Subject: RE: sshd Date: Fri, 11 Sep 1998 18:00:37 +0200 Message-ID: <000001bddd9d$51214220$ca2aa8c0@ripley.tavari.muc.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <35F8BF78.4C32DBEF@rezidew.net> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >ok, now I am just a little bit concerned about this ( maybe I'm over looking something >that's REALLY obvious) . I installed the ssh port from 2.2.5 I had set up tcp wrappers >and noticed that none of the rules for ssh were working so I took the line for it out >of /etc/inetd.conf. The next day I noticed that a 'netstat -a' revealed that sshd was >running on port 22 of my machine. I have done "grep ssh /etc/*" and come >back with only As others have told you, sshd is normaly started as a stand-alone daemon. If you do a man sshd, you'll find the following option: -i Specifies that sshd is being run from inetd. Sshd is normally not run from inetd because it needs to generate the server key before it can respond to the client, and this may take tens of seconds. Clients would have to wait too long if the key was regenerated every time. However, with small key sizes (e.g. 512) using sshd from inetd may be fea- sible hope this helps ... -- Lutz Albers, lutz@muc.de, pgp key available from Do not take life too seriously, you will never get out of it alive. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message