Remove Non-broadcasting ESSID entry since I've fixed that

git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@225 4912f4e0-d625-0410-9fb7-b9a5a253dbdc

1 files changed, 0 insertions, 5 deletions

diff --git a/TODO b/TODO
index 344485328..9c3474dc7 100644
--- a/TODO
+++ b/TODO
@@ -13,11 +13,6 @@ Wireless link checking could be enhanced to check the signal strength of an acce
 There is currently no logic to gracefully recover from a crashed/killed dbus or hal.  There are dbus functions for notification when services come up and go away which could be used here.  Remeber that when dbus dies, hal also dies at the moment.
 
 
-- Deal with blank ESSIDs
-
-Access points can be set not to broadcast their ESSIDs, which the client must know.  These appear as blank ESSIDs to cards doing wireless scanning, even though the rest of the AP's information is known (channel, rate, etc).  There has to be a way to deal with this as many companies do not broadcast ESSIDs for security measures.  Workarounds for this practice could include brute-forcing the Allowed Networks list if no suitable wireless network is found to begin with.  Obviously, there would be no way to detect if a WEP key was wrong, because unless the ESSID and WEP key are both correct, we cannot associate with the access point to see if we have a link.  Code exists to do this for wireless cards that do not support wireless scanning, and this code could be adapted.
-
-
 - Store Allowed Network WEP keys in gnome-keyring
 
 These keys should probably be encrypted, rather than being stored in GConf.