Hot Downloads

×

Notice

The forum is in read only mode.
Welcome, Guest
Username: Password: Remember me

TOPIC:

Re: wireless Networking 17 years 8 months ago #3131

:D
Ok, first of all.
a)I didnt want to start some sort of argument.
b)Mr Chris Partsenidis
Founder & Senior Editor
www.Firewall.cx
I appologise. I didnt realise "what a stupid this to say" was 'uncivilized' 'unacceptable' and 'insulting anyone'.
It clearly wasnt intended for that.
(can i use "silly" next time ?) :?

c)Sahirh, I hope you didnt take what I said as some sort of personal attack, it wasnt. I respect all you comments yourve made in these forums, there excellent.


Ok, after i read your first post, i got this impression:
wireless security is *silly* and hacking into wireless network is *silly*.
which I said thats *silly*.
Where theres a security risk theres a hacker and where theres a hacker theres a security risk.
theres always going to be ppl trying to hack WLANs, and also unsecure WLANS are always going to be there.
I have access to 2 unsecure WLANS from my office. and one from home. I didnt even try!

As for the 2nd post:

I believe that there are bigger problems to worry about than wireless security


Sorry, dont agree.

The way I see it a WLAN is almost as hostile as the Internet


Yup

In short, deal with wireless security for sure, but when you take a break from deciding between WEP, EAP or the latest proprietary security protocol from company Z, please turn off file sharing on your internet facing gateway thank you very much.


Agree, there are other security risks. it would be wrong for someone to concentrate on WLAN over IDS/firewall/whatever . But vice-verca! I think that all security are equally important.
I dont think there is a "bigger problem" in security, one should consider them all equally important.

Anyways having said that, I think WLAN security is relative easy anyways.... at least till you get to VLANs.
Firewall,WEP and access lists is enough for me for WLAN.

Having said all that, I hope this Topic is finished.
:D

Re: wireless Networking 17 years 8 months ago #3134

  • Chris
  • Chris's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 1447
  • Karma: 8
  • Thank you received: 13
hmmz_2000,

Wireless LANs and security, as you seem to be aware of, are a BIG topic!

I personally agree that wireless lans are currently insecure and also believe that they are still immature to justify a major roll out of them throughout a network, especially if we are talking about a large one!!

In the years to come, expect to see some major changes in WiFi security as the protocols supporting (802.11a,b,g) are constantly revised, and this will continue to happen for a while.

We are planning to tackle the WiFi topic very soon and its certainly going to be very interesting with all the information we will uncover to help administrators, members and our visitors, understand WiFi security and how to protect such networks adequately.

Lastly, I'd like to clear things up - There is no intention to make anyone here feel uncomfortable, so don't take my comment in your previous post personally.
We are one big happy community here and we all strive to help each other learn and understand these complex networking concepts.

As you know, we have a strong and respectful team that always goes out of their way to help everyone else, just like a lot of members do the same in these forums.

I hope you enjoy the site, and become a familiar face around here as there is plenty of room for everyone!

Cheers,
Chris Partsenidis.
Founder & Editor-in-Chief
www.Firewall.cx

Re: wireless Networking 17 years 8 months ago #3135

no probs!
all cool :)

anways made a mistake with VLANs ...... i acctually ment VPNs ....

Re: wireless Networking 17 years 8 months ago #3142

  • tfs
  • tfs's Avatar
  • Offline
  • Elite Member
  • Elite Member
  • Posts: 521
  • Thank you received: 0
Darn.

I missed the whole discussion.

Anyway, I agree.

Just kidding.

Anyway, everyone is right - including Sahirh. I don't think you want to get paranoid about the whole issue, but you do need to take precautions.

The biggest problem is that most people set up wifi with 0 (that's zero) security. Wardrivers and warchalkers don't have to get fancy trying to break into a wifi setup that is secure, there are plenty out there that aren't (and it is so easy to set up just the barest of security).

I am not sure about Sahirhs area, but here wifi is big and you could probably drive around most neighborhoods and find one or two. But he is correct about the business environment. They are normally pretty secure buildings - so you can't just go driving around and find an unsecure setup.

What you could do, however, is do a similar thing that Sahirh mentions about walking around and just plugging in to an empty wall connect.

You could just sit outside the office in an empty office or lunch room and connect to an AP inside the office. I was in a lawyers office just the other day and saw a linksys AP sitting on someones desk. Now, if this person didn't have any security on this AP, I could just connect from outside the office (while pretending to wait for someone) and I am inside their network. This is the bane of a network administrators existance - an employee who just brings in a cheap AP from home and sets it on their desk. There goes all the fancy firewalls you have protecting your network - out the window.

Just my 2 cents worth.
Thanks,

Tom

Re: wireless Networking 17 years 8 months ago #3144

Hmmz, no problem mate, I'm not in the habit of taking any of these things to heart -- in fact I hadn't even read your first post, it was edited before I hit this thread.. rest assured you are more than entitled to call me silly and stupid... hehe

Ok now that that stuff is out of the way..
The thrust of my argument was not that wireless security is silly... its merely that with wi-fi touted as the next big thing, and the failure of its security measures really threw it more into the limelight. The insecurity of wireless networks do not come so much from the fact of them being 'wireless' and accessible to an attacker, as from the fact that it was flawed right from the initial design

The original WEP protocol was a joke -- they figured that using a stream cipher where all users share a common static key (which most places is never changed) would be secure. not to mention the initialization vector is a mere 24 bits. It would have been easy for them to sort all this out by using a block cipher, or a cryptographic checksum instead of the stupid CRC-32 linear algorithm that got thrown in..

However the biggest issue came about when the FMS attack (which btw is targetted at RC4 the underlying encryption algo) came round.. you basically only require one byte of plaintext and a few million packetsand you can derive the key. Since 802.11 packets are encapsulated by 802.2 headers -- which haev a constant first byte.. all you need to do is collect the packets to get the key.

In fact this is exactly how tools like Airsnort and WEPcrack work.. ok so then they modified it to incorporate a 104 bit key, and airsnort became ineffective against newer hardware..

Now you have a power void.. and a bunch of contenders to the throne.. you have WPA which provides dynamic keying and key management (thereby reducing the flaw of a static key).. you have 802.1X for authentication.. you have the iEEE's TKIP, which changes keys every hour and the checksum is a crypto algorithm instead of a CRC.. Some people are designing their hardware to support AES.. and I recently read that Cisco is jumping in with their own proprietary protocol..

Whats happened here is that you're left with an array of choices.. each of which solves some part of the whole problem.. everyone is struggling to mix this cocktail of protocols and implementations to provide a standard package.. but its not happened yet (we all know how well standardisation works in the computer industry)..

All this has pushed wi-fi security or i should say insecurity into the limelight.. the insecurity comes not from the wi-fi or radio frequency (RF) layer.. but from the link layer protocols above it ! If you ran WEP over copper cable (lol) it would still be as insecure.. its got nothing to do with the fact that it runs over air waves.. ultimately if you have new equipment and just follow some basic tips (read my post a while back in the security/firewalls forum), its easier to lock down Wi-Fi than to lock down a BIND server. I suppose you chaps have more trouble with rogue access points (what does it cost ? around $150 or so ??) something that hasn't cropped up here.

To end this, ill quote from Firewalls and Internet Security 2nd edition [Cheswick, Bellovin, Rubin]

"it is not clear that the link layer is the right one for security. In a cofeeshop, the security association is terminated by the store: is there any reason to trust the shopkeeper? Perhaps link layer security makes some sense in a home, where you control both the access point and the wireless machines. However, we prefer end-to-end security at the network layer or in the applications

Now I've been a disciple of these guys since the first book, and I don't think anything could sum it up better.. that said, it goes completely against what I normally say.. that applications will always be insecure so ensure nobody malicious can use them.. but this case is an exception.

To make this post a little bit longer and to try and illustrate what Im saying through example (since I dont really know if I've got my point accross)

Scenario:

HaplessVictim Industries are the worldwide leading manufacturers of potted wax candles. I am Wile.E.Hacker and I want to break into their network so I can ship a consignment of fine candles to my friends Chris Partsenidis and Thomas Scheiderich... HaplessVictim recently installed a wi-fi access point so that their CEO can feel 'with the times' while using his brand new Wi-fi enabled laptop around the office.

A quick bit of reconnaisance gives me the whole desert tray....

The webserver is IIS 5.0 vulnerable to WebDav furthermore, they run an online order system which is vulnerable to SQL injection .

The mailserver runs Sendmail and of course hasn't been updated in a while (can you imagine the CEO not being able to read his forwards and email for a day ?) so we have the prescan vulnerability.

The Nameserver is one of my favourite dishes.. good old BIND.. and we have our choice of toppings

The FTP server is Serv-U 5.0.. a "powerful, easy-to-use, award-winning FTP server" created by Rob Beckers (he neglected to mention 'insecure'), it goes well with a portion of MDTM or the site CHMOD vulnerability if you're interested in keeping the calories down.

The Microsoft SQL database server is running on the webserver (gasp), and as usual.. the sa account has a blank password. (Just keep pressing 'next' during the install and you will meet your deadlines).

None of this matters because they have a Big Scary Firewall (tm).. its Checkpoint.. but it turns out its not so scary after all .

The Wi-fi implementation is horribly insecure.. in fact I even have the silly 40 bit WEP key.. its '31337'.. however once i get in using the wireless lan, to do anything useful I still have to break one of the damn application servers using the same method I would have used before ... so why would I even bother with it ? well I could just sit around crashing their Windows workstations with the ASN.1 exploit ..

But then Chris and Tom would never get their candles would they..
;)

I respect your point of view.. but I hope I've illustrated what I'm talking about here...
Sahir Hidayatullah.
Firewall.cx Staff - Associate Editor & Security Advisor
tftfotw.blogspot.com

Re: wireless Networking 17 years 8 months ago #3145

  • tfs
  • tfs's Avatar
  • Offline
  • Elite Member
  • Elite Member
  • Posts: 521
  • Thank you received: 0
And what would I do when my electricity goes out? :lol:
Thanks,

Tom
Time to create page: 0.112 seconds

CCENT/CCNA

Cisco Routers

  • SSL WebVPN
  • Securing Routers
  • Policy Based Routing
  • Router on-a-Stick

VPN Security

  • Understand DMVPN
  • GRE/IPSec Configuration
  • Site-to-Site IPSec VPN
  • IPSec Modes

Cisco Help

  • VPN Client Windows 8
  • VPN Client Windows 7
  • CCP Display Problem
  • Cisco Support App.

Windows 2012

  • New Features
  • Licensing
  • Hyper-V / VDI
  • Install Hyper-V

Linux

  • File Permissions
  • Webmin
  • Groups - Users
  • Samba Setup