From owner-freebsd-security Thu Oct 21 12:53:46 1999 Delivered-To: freebsd-security@freebsd.org Received: from onizuka.vmunix.org (onizuka.vmunix.org [194.221.152.19]) by hub.freebsd.org (Postfix) with ESMTP id 5B53314A18 for ; Thu, 21 Oct 1999 12:53:34 -0700 (PDT) (envelope-from torstenb@vmunix.org) Received: from localhost (1123 bytes) by onizuka.vmunix.org via sendmail with stdio (sender: ) (ident using unix) id for ; Thu, 21 Oct 1999 21:53:40 +0200 (CEST) Message-Id: Date: Thu, 21 Oct 1999 21:53:40 +0200 (CEST) From: torstenb@vmunix.org (Torsten Blum) To: kris@hub.freebsd.org Cc: security@freebsd.org Subject: Re: Kerberos integration into ports--in particular, SSH References: X-Newsreader: NN version 6.5.3 (NOV) Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In freebsd-security you wrote: >> The real gist of my email is that I'd like to see the K4 patches >> incorporated into the SSH port when the user has K4 enabled into >> /etc/make.conf, or if they give a particular command line argument. The >> SSH K4 patches (with AFS, etc) are found at: > >Did you suggest this to the maintainer (torstenb@FreeBSD.org)? Seems like >it can't hurt. I can't test the patches because I don't have access to a Kerberos environment - not to mention the lack of time to test those patches. And it won't ever be the default to include Kerberos in the ssh port - unless the ssh maintainers add it to their codebase. Lack of time and (continuously) test the Kerberos support is probably a problem most of the (port or original) maintainers have. -tb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message