From owner-cvs-all  Fri Feb  5 18:54:51 1999
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA14353
          for cvs-all-outgoing; Fri, 5 Feb 1999 18:54:51 -0800 (PST)
          (envelope-from owner-cvs-all@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14347;
          Fri, 5 Feb 1999 18:54:49 -0800 (PST)
          (envelope-from brian@FreeBSD.org)
From: Brian Somers <brian@FreeBSD.ORG>
Received: (from brian@localhost)
	by freefall.freebsd.org (8.9.2/8.9.2) id SAA00668;
	Fri, 5 Feb 1999 18:54:48 -0800 (PST)
	(envelope-from brian@FreeBSD.org)
Date: Fri, 5 Feb 1999 18:54:48 -0800 (PST)
Message-Id: <199902060254.SAA00668@freefall.freebsd.org>
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Subject: cvs commit: src/usr.sbin/ppp auth.c auth.h bundle.c ccp.c chap.c
         chap.h datalink.c datalink.h descriptor.h hdlc.c ipcp.c link.c
         main.c mbuf.c pap.c pap.h radius.c radius.h vjcomp.c
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

brian       1999/02/05 18:54:48 PST

  Modified files:
    usr.sbin/ppp         auth.c auth.h bundle.c ccp.c chap.c 
                         chap.h datalink.c datalink.h descriptor.h 
                         hdlc.c ipcp.c link.c main.c mbuf.c pap.c 
                         pap.h radius.c radius.h vjcomp.c 
  Log:
  Decouple pap & chap output routines from the corresponding
  input routines and take advantage of the new init/continue
  interface in libradius.  This allows a timely response on
  other links in an MP setup while RADIUS requests are in
  progress as well as the ability to handle other data from
  the peer in parallel.  It should also make the future addition
  of PAM support trivial.
  
  While I'm in there, validate pap & chap header IDs if
  ``idcheck'' is enabled (the default) for other FSM packet
  types.
  
  NOTE: This involved integrating the generation of chap
        challenges and the validation of chap responses
        (and commenting what's going on in those routines).
        I currently have no way of testing ppps ability
        to respond to M$Chap CHALLENGEs correctly, so if
        someone could do the honours, it'd be much
        appreciated (it *looks* ok!).
  
  Sponsored by: Internet Business Solutions Ltd., Switzerland
  
  Revision  Changes    Path
  1.38      +52 -17    src/usr.sbin/ppp/auth.c
  1.15      +20 -7     src/usr.sbin/ppp/auth.h
  1.45      +15 -2     src/usr.sbin/ppp/bundle.c
  1.42      +1 -2      src/usr.sbin/ppp/ccp.c
  1.40      +270 -216  src/usr.sbin/ppp/chap.c
  1.11      +4 -6      src/usr.sbin/ppp/chap.h
  1.29      +24 -25    src/usr.sbin/ppp/datalink.c
  1.6       +2 -2      src/usr.sbin/ppp/datalink.h
  1.5       +2 -1      src/usr.sbin/ppp/descriptor.h
  1.38      +3 -3      src/usr.sbin/ppp/hdlc.c
  1.71      +1 -4      src/usr.sbin/ppp/ipcp.c
  1.7       +1 -2      src/usr.sbin/ppp/link.c
  1.150     +3 -1      src/usr.sbin/ppp/main.c
  1.23      +2 -7      src/usr.sbin/ppp/mbuf.c
  1.31      +126 -92   src/usr.sbin/ppp/pap.c
  1.9       +3 -4      src/usr.sbin/ppp/pap.h
  1.3       +244 -109  src/usr.sbin/ppp/radius.c
  1.2       +13 -3     src/usr.sbin/ppp/radius.h
  1.25      +1 -2      src/usr.sbin/ppp/vjcomp.c

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message