From owner-freebsd-current Thu Jun 21 13:20:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-13.dsl.lsan03.pacbell.net [63.207.60.13]) by hub.freebsd.org (Postfix) with ESMTP id 8053D37B403 for ; Thu, 21 Jun 2001 13:20:50 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A37A666B21; Thu, 21 Jun 2001 13:20:49 -0700 (PDT) Date: Thu, 21 Jun 2001 13:20:49 -0700 From: Kris Kennaway To: Dag-Erling Smorgrav Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: HEADS UP!! S/Key is ancient, OPIE is new Message-ID: <20010621132049.C52345@xor.obsecurity.org> References: <200106201900.f5KJ0X608864@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Thu, Jun 21, 2001 at 11:52:52AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jun 21, 2001 at 11:52:52AM +0200, Dag-Erling Smorgrav wrote: > Mark Murray writes: > > I want to remove S/Key from CURRENT completely, and replace it > > with OPIE where necessary. > > How will this affect OpenSSH's SKeyAuthentication option, which is > required for certain types of token-based authentication (like > CryptoCard)? It already uses OPIE; AFAIK OpenBSD decided to call OPIE S/Key when they imported it to replace their old S/Key. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message