RE: CAPWAP Problem Statement (secure download?)
From: Bob O'Hara (bobairespace.com)
Date: 18 Aug 2003 18:08:40 -0000
TGi (802.11i task group) has nothing at all to do with the security of
the code in the AP, or of its download and installation.  Without some
method to secure and authenticate the code, the possibility exists (and
some script kiddie will exploit it) to download code to the AP that
plays "Oh Suzanna" in the key of 2.4 GHz.

 -Bob
 

-----Original Message-----
From: Martin Lefkowitz [mailto:lefko [at] trapezenetworks.com] 
Sent: Monday, August 18, 2003 10:45 AM
To: lwapp [at] frascone.com
Subject: Re: [Lwapp] CAPWAP Problem Statement (secure download?)


I also am wondering why we need a secure download?

Given TGi's basic linchpin of mutual authentication I wonder what good
it 
would do to have rogue code in an AP that can not authenticate itself to

the AR in it's operational state, or authenticate itself of the STA in
it's 
operational state.  However, I do see significant danger in putting 
something like a certificate in a physically insecure device (like in a 
hotspot) where it could be broken into and have the certificate
compromised.

Seems to me that the CAPWAP doc should concentrate of getting the image 
downloaded reliably, not securely.  The security part come in play in
the 
operational state.

Marty

_______________________________________________
Lwapp mailing list
Lwapp [at] frascone.com
http://mail.frascone.com/mailman/listinfo/lwapp

Results generated by Tiger Technologies using MHonArc.