From owner-freebsd-security Thu Jun 3 10: 5: 0 1999 Delivered-To: freebsd-security@freebsd.org Received: from guepardo.vicosa.com.br (guepardo.tdnet.com.br [200.236.148.6]) by hub.freebsd.org (Postfix) with ESMTP id 2D97415210 for ; Thu, 3 Jun 1999 10:04:47 -0700 (PDT) (envelope-from kernel@tdnet.com.br) Received: from tdnet.com.br [200.236.148.203] by guepardo.vicosa.com.br with ESMTP (SMTPD32-5.00) id A87430E0096; Thu, 03 Jun 1999 14:16:36 -0300 Message-ID: <37568B58.C48DCEA2@tdnet.com.br> Date: Thu, 03 Jun 1999 14:04:08 +0000 From: Unknow User X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.8-STABLE i386) MIME-Version: 1.0 To: freebsd-security@freebsd.org Subject: SSH2 (in FreeBSD-Questions) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following was running at Questions: login.conf is all fine and dandy, but... SSH2 doesn't support using login, SSH1 did, I don't know why they removed it, I rather liked it. So people logging in with SSH2 wouldn't be affected by anything in login.conf...Unless there's some hidden feature in SSH2 that lets it use login, I'm screwed, or I only run SSH1, unfortunately, most windows ssh clients default to SSH2 protocol from what I've seen. I don't expect them to enjoy that.. =P -**- What is this? Isn't the OS supposed to be robust enough to handle that! How is possible to write a software that can bypass system limits imposed by sysadmin? how is it implemented? So this implementation is insecure, once it ALLOW user level programs run over it! Can anybody explain me it? Thanks a lot! -- "The box said 'Requires Windows 98, NT, Linux or better' so I installed FreeBSD." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message