| RE: RE: [Isms] RADIUS is not a trusted third party | <– Date –> <– Thread –> |
|
From: Bernard Aboba (aboba |
|
| Date: Fri, 22 Apr 2005 00:51:34 -0400 (EDT) | |
> Yet NAS takes "go/no-go" decision from RADIUS, and takes the keys to > talk to the client... If this is not trust - what is it? There is no IETF standard defining how keys are provided within RADIUS for exactly that reason -- there is no trust relationship defined when a proxy is present. The "Housley Criteria" described in RFC 4017 do not allow disclosure of keys to additional parties. The problem does not exist in Diameter EAP, which enables keys to be provided directly without access by proxies.
- Re: RE: [Isms] RADIUS is not a trusted third party, (continued)
- Re: RE: [Isms] RADIUS is not a trusted third party John Vollbrecht, April 21 2005
-
RE: RE: [Isms] RADIUS is not a trusted third party Bernard Aboba, April 21 2005
- Re: RE: [Isms] RADIUS is not a trusted third party Julien Bournelle, April 22 2005
- Re: RE: [Isms] RADIUS is not a trusted third party Bernard Aboba, April 22 2005
- Message not available
- Re: RE: [Isms] RADIUS is not a trusted third party Bernard Aboba, April 22 2005
Results generated by Tiger Technologies using MHonArc.