Date: Wed, 16 Feb 2005 19:50:34 +0900 (JST) From: Yamamoto Shigeru <shigeru@iij.ad.jp> To: brooks@one-eyed-alien.net Cc: ports@freebsd.org Subject: Re: update patch of security/wpa_supplicant, from 0.3.0 to 0.3.8 Message-ID: <20050216.195034.21935248.shigeru@iij.ad.jp> In-Reply-To: <20050216071340.GB18826@odin.ac.hmc.edu> References: <20050216.115303.39149829.shigeru@iij.ad.jp> <20050216071340.GB18826@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "Brooks" == Brooks Davis <brooks@one-eyed-alien.net> writes: Brooks> Thanks for you submission. I've committed these parts along with Brooks> some fixes. Thank you. >> - install start/stop script Brooks> I did not commit this because I believe this is the wrong way to Brooks> integrate wpa_supplication. The integration needs to take place in Brooks> /etc/rc.d/netif so wpa supplicant is started on interfaces when they Brooks> arrive, not at boot since they may not exist until arbitrarily Brooks> later. I think it is better to separate wpa_supplicant start/stop script from netif script. Because, we sometimes need to restart wpa_supplicant when changing WEP key. In our company, in which we can't use WPA, WEP key is sometimes changed to be more secure. In this case, we need restarting wpa_supplicant to change WEP key. I think it is populer to change WEP key frequently in none-WPA/802.11i environment. So, it is useful to separate wpa_supplicant start/stop script from netif script. Thanks, ------- YAMAMOTO Shigeru <shigeru@iij.ad.jp>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050216.195034.21935248.shigeru>