Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] WiFi considerations
- Date: Thu, 12 Jul 2007 23:44:41 +0900
- From: "Josh Glover" <jmglov@example.com>
- Subject: Re: [tlug] WiFi considerations
- References: <20070709175552.070d5b94.gstewart@bonivet.net> <20070710222206.GA29191@aidi.santinoli.com> <20070711114636.6dd1798c.gstewart@bonivet.net> <d8fcc0800707110335p18813045w4c875ddb7f231253@mail.gmail.com> <20070711125312.97ed6288.gstewart@bonivet.net> <d8fcc0800707110450mab781edw1415660332ca7d95@mail.gmail.com> <20070711123615.GA11625@aidi.santinoli.com>
On 11/07/07, David Santinoli <marauder@example.com> wrote:
However, data encryption - in your case implemented at the application layer - is only one aspect of security here. Another one, not less important, is authentication: after the wardriver-of-the-day succeeds in associating with your unprotected AP and manages to get an address in your LAN, he might not be able to SSH into your server, but he can abuse your Internet connection, which might be even more harmful.
Of course, he has to discover my laptop's MAC (which he can probably do with an ARP flood), spoof it (easy on Linux, dunno on Windows), and DOS my 'top (probably hard, unless he has a botnet).
So yes, my network is insecure. But then again, so is any network connected to the outside world. :)
But I think my layer of making shite difficult for the bad guys is enough to ensure that the wardriver chooses one of these nice networks instead:
: jmglov@example.com; sudo iwlist eth1 scan eth1 Scan completed : Cell 01 - Address: 00:16:CF:69:78:6D ESSID:"YBBUser" Protocol:IEEE 802.11bg Mode:Master Channel:3 Encryption key:off Bit Rate:1Mb/s Bit Rate:2Mb/s Bit Rate:5.5Mb/s Bit Rate:6Mb/s Bit Rate:9Mb/s Bit Rate:11Mb/s Bit Rate:12Mb/s Bit Rate:18Mb/s Bit Rate:24Mb/s Bit Rate:36Mb/s Bit Rate:48Mb/s Bit Rate:54Mb/s Quality:100/0 Signal level:-20 dBm Noise level:-256 dBm Extra: Last beacon: 51ms ago Cell 02 - Address: 00:A0:B0:4E:98:8B ESSID:"washima" Protocol:IEEE 802.11g Mode:Master Channel:6 Encryption key:off Bit Rate:1Mb/s Bit Rate:2Mb/s Bit Rate:5.5Mb/s Bit Rate:6Mb/s Bit Rate:9Mb/s Bit Rate:11Mb/s Bit Rate:12Mb/s Bit Rate:18Mb/s Bit Rate:24Mb/s Bit Rate:36Mb/s Bit Rate:48Mb/s Bit Rate:54Mb/s Quality:79/0 Signal level:-50 dBm Noise level:-256 dBm Extra: Last beacon: 7ms ago
-- Cheers, Josh
- Follow-Ups:
- Re: [tlug] WiFi considerations
- From: David Santinoli
- References:
- [tlug] WiFi considerations
- From: Godwin Stewart
- Re: [tlug] WiFi considerations
- From: David Santinoli
- Re: [tlug] WiFi considerations
- From: Godwin Stewart
- Re: [tlug] WiFi considerations
- From: Josh Glover
- Re: [tlug] WiFi considerations
- From: Godwin Stewart
- Re: [tlug] WiFi considerations
- From: Josh Glover
- Re: [tlug] WiFi considerations
- From: David Santinoli
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] Firefox a security risk when combined with IE?
- Next by Date: Re: [tlug] [OT] Say _no_ to the Microsoft Office format as an ISO standard
- Previous by thread: Re: [tlug] WiFi considerations
- Next by thread: Re: [tlug] WiFi considerations
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links