Date: Thu, 27 Jun 2002 18:07:17 -0700 (PDT) From: Jason Stone <jason-fbsd-security@shalott.net> To: =?iso-8859-1?Q?Arvinn_L=F8kkebakken?= <arvinn@rns.no> Cc: <freebsd-security@FreeBSD.ORG> Subject: Re: Re[2]: openssh OR openssh-portable Message-ID: <20020627180217.X2226-100000@walter> In-Reply-To: <002501c21e38$1be59db0$0201a8c0@dus>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I still don't understand the difference. According to the OpenSSH's > website the portable version is for other operating systems (than > OpenBSD i assume). Why is it then possible to use the "not portable" > version of OpenSSH on FreeBSD? We were able to use the native openbsd version because freebsd is close enough to openbsd that little patching was necesary. > By reading this I understand that the p release (openssh-portable) is not as > clean as the other one. What are the benefits running the p release on > FreeBSD systems when both releases works? OpenBSD doesn't use pam, and therefor openssh native doesn't either. Since most other systems _do_ use pam, openssh-portable does. FreeBSD uses pam, so it seems to make the most sense to just use openssh portable. -Jason ----------------------------------------------------------------------- I worry about my child and the Internet all the time, even though she's too young to have logged on yet. Here's what I worry about. I worry that 10 or 15 years from now, she will come to me and say "Daddy, where were you when they took freedom of the press away from the Internet?" -- Mike Godwin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: See https://private.idealab.com/public/jason/jason.gpg iD8DBQE9G7bFswXMWWtptckRApifAJwPAR11iEKbvhUOO4K9VaRJIAIlCACfYlz4 CrnIvxyT5Vqsq3v0USLHD+M= =tpFy -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020627180217.X2226-100000>