| RE: RE: [Isms] RADIUS is not a trusted third party | <– Date –> <– Thread –> |
|
From: Bernard Aboba (aboba |
|
| Date: Mon, 25 Apr 2005 12:00:24 -0400 (EDT) | |
> The use of RADIUS itself without a defined extension such as EAP-TLS or > EAP-PEAP over RADIUS cannot securely pass attributes between entities. Note > that the defined EAP-TLS (or other EAP mechanisms) over RADIUS provides for > secure attribute passing between entities even through proxies. EAP does not affect how RADIUS attributes are passed, nor does it enable the passing of RADIUS attributes between the EAP peer and server. So as far as RADIUS attributes are concerned, what EAP method is used, or whether EAP is used does not affect RADIUS security, except that an EAP-Message attribute is included in the messages. Also, EAP-TLS does not permit passing of TLVs between the peer and server; this is only allowed in tunneled mechanisms such as EAP-TTLS and PEAP.
- Re: RE: [Isms] RADIUS is not a trusted third party, (continued)
- Re: RE: [Isms] RADIUS is not a trusted third party Bernard Aboba, April 22 2005
-
RE: RE: [Isms] RADIUS is not a trusted third party Bernard Aboba, April 21 2005
- Message not available
- 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 Nelson, David, April 22 2005
- RE: RE: [Isms] RADIUS is not a trusted third party Bernard Aboba, April 25 2005
-
RE: RE: [Isms] RADIUS is not a trusted third party Glen Zorn (gwz), April 25 2005
- RE: RE: [Isms] RADIUS is not a trusted third party Bernard Aboba, April 25 2005
-
RE: RE: [Isms] RADIUS is not a trusted third party Glen Zorn (gwz), April 26 2005
- RE: RE: [Isms] RADIUS is not a trusted third party Bernard Aboba, April 26 2005
Results generated by Tiger Technologies using MHonArc.