updates from Farrell Woods

diff --git a/README.MSCHAP80 b/README.MSCHAP80
index b0d54cbecd2bb26915f8c93c2c18b0e85d675c71..d3ed291b73a757febcbcff04756e9e1fda1614ad 100644 (file)
--- a/README.MSCHAP80
+++ b/README.MSCHAP80
@@ -4,6 +4,7 @@ PPP Client Support for Microsoft's CHAP-80
 Eric Rosenquist          rosenqui@strataware.com
 (updated by Paul Mackerras)
 (updated by Al Longyear)
 Eric Rosenquist          rosenqui@strataware.com
 (updated by Paul Mackerras)
 (updated by Al Longyear)

+(updated by Farrell Woods)

 
 INTRODUCTION
 
 
 INTRODUCTION
 


@@ -45,8 +46,23 @@ place, but I didn't need it myself so I didn't implement it.
 BUILDING THE PPPD
 
 MS-CHAP uses a combination of MD4 hashing and DES encryption for
 BUILDING THE PPPD
 
 MS-CHAP uses a combination of MD4 hashing and DES encryption for

-authentication.  You'll need to get Eric Young's libdes library in
-order to use my MS-CHAP extensions.  You can find it in:
+authentication.  You may need to get Eric Young's libdes library in
+order to use my MS-CHAP extensions.  A lot of UNIX systems already
+have DES encryption available via the crypt(3), encrypt(3) and
+setkey(3) interfaces.  Some may (such as that on Digital UNIX)
+provide only the encryption mechanism and will not perform
+decryption.  This is okay.  We only need to encrypt to perform
+MS-CHAP authentication.
+
+If you have encrypt/setkey available, then hopefully you need only
+define these two things in your Makefile: -DUSE_CRYPT and -DCHAPMS.
+Skip the paragraphs below about obtaining and building libdes.  Do
+the "make clean" and "make" as described below.  Linux users
+should not need to modify their Makefiles.  Instead,
+just do "make CHAPMS=1 USE_CRYPT=1".
+
+If you don't have encrypt and setkey, you will need Eric Young's
+libdes library.  You can find it in:

 
 ftp://ftp.funet.fi/pub/crypt/mirrors/ftp.psy.uq.oz.au/DES/libdes-3.06.tar.gz
 
 
 ftp://ftp.funet.fi/pub/crypt/mirrors/ftp.psy.uq.oz.au/DES/libdes-3.06.tar.gz
 


@@ -60,6 +76,8 @@ I used libdes-3.06, but hopefully anything newer than that will work
 also.  Get the library, build and test it on your system, and install
 it somewhere (typically /usr/local/lib and /usr/local/include).
 
 also.  Get the library, build and test it on your system, and install
 it somewhere (typically /usr/local/lib and /usr/local/include).
 

+
+

 You should now be ready to (re)compile the PPPD.  Go to the pppd
 subdirectory and make sure the Makefile contains "-DCHAPMS" in the
 CFLAGS or COMPILE_FLAGS macro, and that the LIBS macro (or LDADD for
 You should now be ready to (re)compile the PPPD.  Go to the pppd
 subdirectory and make sure the Makefile contains "-DCHAPMS" in the
 CFLAGS or COMPILE_FLAGS macro, and that the LIBS macro (or LDADD for


@@ -172,6 +190,12 @@ library.  If DES checks out, the md4.c routines are probably failing
 (system byte ordering may be a problem) or my code is screwing up.  I've
 only got access to a Linux system, so you're on your own for anything else.
 
 (system byte ordering may be a problem) or my code is screwing up.  I've
 only got access to a Linux system, so you're on your own for anything else.
 

+Another thing that might cause problems is that some RAS servers won't
+respond at all to LCP config requests without seeing the word "CLIENT"
+from the other end.  If you see pppd sending out LCP config requests
+without getting any reply, try putting something in your chat script
+to send the word CLIENT after the modem has connected.
+

 If everything compiles cleanly, but fails at authentication time, then
 it might be a case of the MD4 or DES code screwing up.  The following
 small program can be used to test the MS-CHAP code to see if it
 If everything compiles cleanly, but fails at authentication time, then
 it might be a case of the MD4 or DES code screwing up.  The following
 small program can be used to test the MS-CHAP code to see if it


@@ -186,7 +210,7 @@ produces a known response:
 
 int main(argc, argv)
     int     argc;
 
 int main(argc, argv)
     int     argc;

-    char    *argv[0];
+    char    *argv[];

 {
     u_char          challenge[8];
     int             challengeInt[sizeof(challenge)];
 {
     u_char          challenge[8];
     int             challengeInt[sizeof(challenge)];

diff --git a/README.osf b/README.osf
index ab6919c32919bac1b55ef142b99d9bd5f06d751e..8780604d3bf820ed810b1d415001dd1c4e7cbf77 100644 (file)
--- a/README.osf
+++ b/README.osf
@@ -2,21 +2,16 @@ This file (README.osf) contains instructions for installing ppp-2.3 on a
 Digital Alpha-based system running Digital UNIX (aka DEC OSF/1)
 version 2.0 through version 3.2F.  Digial UNIX version 3.2G and beyond
 are not supported by this package, since PPP is an integral component
 Digital Alpha-based system running Digital UNIX (aka DEC OSF/1)
 version 2.0 through version 3.2F.  Digial UNIX version 3.2G and beyond
 are not supported by this package, since PPP is an integral component

-of those releases.
+of those releases.  (Although it *is* possible to install this software
+on V3.2G and later of Digital UNIX, I would discourage this activity
+because it's likely to break the "update install" feature of Digital
+UNIX.  You were warned...)

 
 

-If you would like to be on a mailing list concerning the ppp package,
-send mail to srt@cs.unt.edu and let me know.  This mailing list should
-not have any regular traffic --- I will use it only if bugs are reported
-to notify everyone of bug-fixes.
+If you encounter bugs in this using this PPP package under Digital
+UNIX then please let me (ftw@zk3.dec.com) know.  I can't promise
+quick turnaround but I should be able to address issues eventually.

 
 

-Note for users of the ppp-2.1.2 package:  I have included a fix
-for the non-STREAMS tty drivers in this release.  If you were using
-version 2.1.2 with a hardware serial port, then you probably used the
-"rlogin-kludge" that I described in the README that came with 2.1.2.
-You don't need this any more, and will have a more efficient connection
-if you get rid of this old work-around.
-
-Below are the steps for installing PPP on a DEC AXP system running OSF/1.
+Below are the steps for installing PPP on Digital UNIX.

 You must do all of the following as "root".
 
 1.  Make the kernel sources, daemon, chat, and pppstat program by typing 
 You must do all of the following as "root".
 
 1.  Make the kernel sources, daemon, chat, and pppstat program by typing 


@@ -104,10 +99,6 @@ You must do all of the following as "root".
 
 9.  Reboot and you're ready to go!
 
 
 9.  Reboot and you're ready to go!
 

-Hopefully, that should work with no hitches.  If there are problems, or
-if I have made a mistake in these instructions, please let me know.
-
-Steve Tate
-University of North Texas
-srt@cs.unt.edu
+Hopefully, that should work with no hitches.  If you find any bugs, or
+errors in these instructions, contact Farrell Woods <ftw@zk3.dec.com>.