Page MenuHomeFreeBSD

ppp: Permit CHAP challenges up to 255 bytes
AcceptedPublic

Authored by jhb on Wed, May 20, 7:31 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Jun 5, 3:42 PM
Unknown Object (File)
Thu, Jun 4, 6:34 AM
Unknown Object (File)
Sat, May 30, 10:05 PM
Unknown Object (File)
Fri, May 29, 1:14 PM
Unknown Object (File)
Thu, May 28, 8:54 PM
Unknown Object (File)
Wed, May 27, 10:14 AM
Unknown Object (File)
Tue, May 26, 3:22 PM
Unknown Object (File)
Mon, May 25, 5:42 PM
Subscribers

Details

Reviewers
emaste
des
Summary

RFC 1994 does not place any limit on the length of the value field in
challenge messages except that the length is a single octet which
bounds the maximum length to 255.

NB: I'm not sure why the local[] and peer[] arrays contain room for an
authentication name (AUTHLEN) in addition to a challenge value/response,
but I've just left that in place.

PR: 271955
Reported by: Robert Morris <rtm@lcs.mit.edu>

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 73707
Build 70590: arc lint + arc unit

Event Timeline

jhb requested review of this revision.Wed, May 20, 7:31 PM
usr.sbin/ppp/chap.c
241

The cast is required so that the single char is promoted to an unsigned int instead of a signed int when passed as the length.

des added a subscriber: des.

It's safe to drop the extra AUTHLEN from challenge.local and challenge.peer

This revision is now accepted and ready to land.Fri, Jun 5, 3:40 PM
This revision now requires review to proceed.Fri, Jun 5, 3:53 PM
This revision is now accepted and ready to land.Fri, Jun 5, 4:40 PM