October 2002
Intermediate to advanced
206 pages
8h 30m
English
Content preview from RADIUSBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
The Access-Request Packet
There is no verification or authentication of the RADIUS
Access-Request
packet, as per the RFC specification, by default. The RADIUS server
will perform a check to ensure that the message originated from an IP
address listed as one of its clients, but in this day and age,
spoofed IP addresses are easy to find and use. This is a serious
limitation of the RADIUS protocol design.
As of now, the only workable solution is to require the presence of
the Message-Authenticator attribute in all
Access-Request messages. Briefly, the
Message-Authenticator is the MD5 hash of the
entire Access-Request message, using the
client’s shared secret as the key. When a RADIUS
server is configured to only accept Access-Request
messages with a valid Message-Authenticator
attribute present, it must silently discard those packets with
invalid or missing attributes. More information on the
Message-Authenticator attribute can be found in
Chapter 9 or in the RFC 2869.
If your implementation somehow prevents the use of the
Message-Authenticator attribute, at least consider
using some sort of account-lockout feature, which disables
authentications after a specified number of authentication attempts
within a specified time.
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.