blank.gif (43 bytes)

Church Of The
Swimming Elephant

Search:
2.2.1. Authenticate-Request Connected: An Internet Encyclopedia
2.2.1. Authenticate-Request

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1334
Up: 2. Password Authentication Protocol
Up: 2.2. Packet Format
Prev: 2.2. Packet Format
Next: 2.2.2. Authenticate-Ack and Authenticate-Nak

2.2.1. Authenticate-Request

2.2.1. Authenticate-Request

Description

The Authenticate-Request packet is used to begin the Password Authentication Protocol. The link peer MUST transmit a PAP packet with the Code field set to 1 (Authenticate-Request) during the Authentication phase. The Authenticate-Request packet MUST be repeated until a valid reply packet is received, or an optional retry counter expires.

The authenticator SHOULD expect the peer to send an Authenticate- Request packet. Upon reception of an Authenticate-Request packet, some type of Authenticate reply (described below) MUST be returned.

    Implementation Note: Because the Authenticate-Ack might be lost, the authenticator MUST allow repeated Authenticate- Request packets after completing the Authentication phase. Protocol phase MUST return the same reply Code returned when the Authentication phase completed (the message portion MAY be different). Any Authenticate-Request packets received during any other phase MUST be silently discarded. When the Authenticate-Nak is lost, and the authenticator terminates the link, the LCP Terminate-Request and Terminate- Ack provide an alternative indication that authentication failed.

A summary of the Authenticate-Request packet format is shown below. The fields are transmitted from left to right.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Code      |  Identifier   |            Length             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Peer-ID Length|  Peer-Id ...
   +-+-+-+-+-+-+-+-+-+-+-+-+
   | Passwd-Length |  Password  ...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+

Code

1 for Authenticate-Request.

Identifier

The Identifier field is one octet and aids in matching requests and replies. The Identifier field MUST be changed each time an Authenticate-Request packet is issued.

Peer-ID-Length

The Peer-ID-Length field is one octet and indicates the length of the Peer-ID field.

Peer-ID

The Peer-ID field is zero or more octets and indicates the name of the peer to be authenticated.

Passwd-Length

The Passwd-Length field is one octet and indicates the length of the Password field.

Password

The Password field is zero or more octets and indicates the password to be used for authentication.


Next: 2.2.2. Authenticate-Ack and Authenticate-Nak

Connected: An Internet Encyclopedia
2.2.1. Authenticate-Request

Cotse.Net

Protect yourself from cyberstalkers, identity thieves, and those who would snoop on you.
Stop spam from invading your inbox without losing the mail you want. We give you more control over your e-mail than any other service.
Block popups, ads, and malicious scripts while you surf the net through our anonymous proxies.
Participate in Usenet, host your web files, easily send anonymous messages, and more, much more.
All private, all encrypted, all secure, all in an easy to use service, and all for only $5.95 a month!

Service Details

 
.
www.cotse.com
Have you gone to church today?
.
All pages ©1999, 2000, 2001, 2002, 2003 Church of the Swimming Elephant unless otherwise stated
Church of the Swimming Elephant©1999, 2000, 2001, 2002, 2003 Cotse.com.
Cotse.com is a wholly owned subsidiary of Packetderm, LLC.

Packetderm, LLC
210 Park Ave #308
Worcester, MA 01609