(RADIATOR) Patch against 3.13 to support per-client TACACS+ keys

[Mike McCauley]

Hello James,

On Sunday 09 October 2005 10:20, James FitzGibbon wrote:
> On 8-Oct-05, at 3:20 AM, Mike McCauley wrote:
> > This looks useful and interesting (and backwards compatible!)
> > I think the only thing I would suggest is that the client-specific
> > tacacs key
> > be kept in a different parameter than Secret, say in TacacsKey.
> > Otherwise you
> > could not have a Tacacs and Radius client on the same box unless
> > they had the
> > same secret/key. What do you think?
>
> Good point; I hadn't figured on that, but that's what you get for
> designing for your own network instead of the general case.
>
> I'll make that change and re-submit.  It will be a bit bigger since
> I'm guessing I'll have to modify Radius/Client.pm as well to allow
> the new key...
No problem.
If you will use a unified diff (diff -u) and send it as an attachment, it will 
really help.

Cheers.

>
> Thanks
>
> --
> j.

-- 
Mike McCauley                               mikem at open.com.au
Open System Consultants Pty. Ltd            Unix, Perl, Motif, C++, WWW
9 Bulbul Place Currumbin Waters QLD 4223 Australia   http://www.open.com.au
Phone +61 7 5598-7474                       Fax   +61 7 5598-7070

Radiator: the most portable, flexible and configurable RADIUS server 
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, 
TTLS, PEAP etc on Unix, Windows, MacOS etc.

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.