From owner-freebsd-current Mon Mar 6 5:58:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.251.241]) by hub.freebsd.org (Postfix) with ESMTP id 46CD637BD6F for ; Mon, 6 Mar 2000 05:58:04 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id IAA08880; Mon, 6 Mar 2000 08:57:54 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38C3B962.F44E0B92@acm.org> Date: Mon, 06 Mar 2000 08:57:54 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: openssh question References: <200003060618.XAA56131@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > First, how does one enable TIS/SKEY authorization for ssh? It appears > that the frst step would be to add -DSKEY to the Makefile conditional > on something. Are there other steps? > Yes, there are other steps. openssh depends upon functions in the openbsd libskey that we do not have. These functions appear to have been added somewhere between our initial version of skey and openbsd's as they exist in openbsd's initial version, but not ours. The skey support in the openssh port has the exact same problems. That being said, if there is some demand for this, I could merge openbsd's libskey into ours and get the skey authentication working. Jim Bloom bloom@acm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message