Thread View: comp.protocols.ppp
2 messages
2 total messages
Started by Jamey Maze
Thu, 20 Aug 1992 17:47
PAP & CHAP
Author: Jamey Maze
Date: Thu, 20 Aug 1992 17:47
Date: Thu, 20 Aug 1992 17:47
18 lines
1209 bytes
1209 bytes
Could someone explain to me the benefit of PAP/CHAP authentication to a user of a dial-up end-node (e.g., a workstation dialing into a company LAN)? Doesn't it just provide a second level of authentication? And I suppose it also allows you to enforce a particular IP address on the dial-in user. Is that pretty much it? Thanks! -- Jamey Maze | Computing & Telecommunications Division Oak Ridge National Lab | Advanced Technology Group P.O. Box 2008, MS-6238 | Internet: jnm@ornl.gov Oak Ridge, TN 37831-6238 | 615/574-6355, FAX 615/574-9646 "The defense of individual rights has reached such extremes as to make society as a whole defenseless against certain individuals. It is time, in the West, to defend not so much human rights as human obligations." - Aleksandr Solzhenitsyn
Re: PAP & CHAP
Author: Dennis Allard
Date: Fri, 21 Aug 1992 18:22
Date: Fri, 21 Aug 1992 18:22
38 lines
2473 bytes
2473 bytes
mhump@sparky.msfc.nasa.gov (Mark Humphries) writes: someone else had written: > > Could someone explain to me the benefit of PAP/CHAP authentication ... > > Password Athentication Protocol (PAP) uses a username and password pair > for user validation. ... > > Challenge-Handshake Authentication Protocol (CHAP) uses a "secret" that > is known by the peer (the host attempting to dial in) and the authenticator > (PPP server/host being dialed into). ... An important issue here has to do with what level connections are being made at (application vs. session or transport) and whether or not human intervention is appropriate or convenient each time a connectio is made. I am new to protocols, new to this newsgroup, and know little about PPP, but here is my two cents on this matter. I got interested in protocols because I recently built my a session level message protocol over Unix sockets (TCP/IP) and an RPC protocol over that. This was in the context of an Emacs/Lisp interface. In this application, new connections are being made at the session level, and are often made by processes without the intervention of a human. The nature of the connection permits complete access to a Lisp address space by a different Lisp or Emacs running anywhere on the internet. Although we have not exported this facility yet, we initially put in a very simple 'password' scheme, consisting of an integer, which the server end of a new connection knows and which the client end must send to connect. (Once a connection is made, the server and client have completely symmetrice roles). Typically, we just use the integer 0, inhouse, since we trust each other. In considering how to provide a more secure connection mechanism, I was intriqued to see this discussion in this newsgroup, which, I repeat, I just joined. I will follow this with interest and try to learn more about PPP. Maybe that's what I should be using. Dennis allard@isi.edu
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads