Freeradius ships with a dictionary file named dictionary.unix, that contains the following attributes: VENDOR Unix 4 BEGIN-VENDOR Unix ATTRIBUTE Unix-FTP-UID 10 integer ATTRIBUTE Unix-FTP-GID 11 integer ATTRIBUTE Unix-FTP-Home 12 string ATTRIBUTE Unix-FTP-Shell 13 string ATTRIBUTE Unix-FTP-Group-Names 14 string ATTRIBUTE Unix-FTP-Group-Ids 15 string END-VENDOR Unix Is the goal of this set of attributes to enable a Radius server to send back UID, GID, etc. information for a user that has been authenticated by the RADIUS server? If so, why use FTP in the name of the attributes? I mean, a Radius server will not be able to know whether the users being authenticated is accessing the target system via FTP, or some other service, right?
On Apr 29, 2019, at 1:06 PM, Full Name <nuncestbibendum@excite.com> wrote:
Freeradius ships with a dictionary file named dictionary.unix, that contains the following attributes:
Yes, we know. There's no need to post configuration files to the list.
Is the goal of this set of attributes to enable a Radius server to send back UID, GID, etc. information for a user that has been authenticated by the RADIUS server? If so, why use FTP in the name of the attributes? I mean, a Radius server will not be able to know whether the users being authenticated is accessing the target system via FTP, or some other service, right?
IIRC, the dictionary was used by some FTP server ~20 years ago. I don't think it's been used for anything since. And no, the *name* of the attribute is irrelevant. It doesn't mean anything. Alan DeKok.
participants (2)
-
Alan DeKok -
Full Name