From owner-freebsd-security Wed Jun 3 16:50:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02566 for freebsd-security-outgoing; Wed, 3 Jun 1998 16:50:09 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from red.juniper.net (red.juniper.net [208.197.169.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02450 for ; Wed, 3 Jun 1998 16:49:52 -0700 (PDT) (envelope-from pst@juniper.net) Received: from base.juniper.net (base.juniper.net [208.197.169.208]) by red.juniper.net (8.8.5/8.8.5) with ESMTP id QAA10767; Wed, 3 Jun 1998 16:48:48 -0700 (PDT) Received: (from pst@localhost) by base.juniper.net (8.8.8/8.7.3) id QAA06307; Wed, 3 Jun 1998 16:48:48 -0700 (PDT) To: freebsd-security@FreeBSD.ORG Subject: radius/OTP framework vs checkuserpassword() From: Paul Traina Date: 03 Jun 1998 16:48:47 -0700 Message-ID: <7yg1hmm4gw.fsf@base.juniper.net> Lines: 12 X-Mailer: Gnus v5.4.37/XEmacs 19.16 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Actually, We (Juniper) have already commissioned a RADIUS client implementation for FreeBSD that we intend to contribute back. Part of this is an authentication framework/API so that we can handle both challenge/response and shared secret authentication methods. The framework and API are still in design specification stage. Qualified (by me) FreeBSD security folk who want to review the document once we're ready with a draft spec should send a note to me. Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message