asemisldkfj
the law is no protection
what do you know about it?
I ordered a Linksys WRT54G-L router to act as the wireless access point (still behind OpenBSD via ethernet) for my home network, and I am thinking about forgoing my current method of WEP + OpenVPN and solely using WPA(2?).
I'm Googling around now to see what people are saying about it.
the purchase of the router was motivated by the pain in the butt that PCI wireless cards have been (having to ifconfig down && ifconfig up every once in a while, having to reboot the router for wireless to resume functioning, etc.) and my OpenVPN client on my Mac dropping the OpenVPN connection seemingly randomly and when I run rsync over ssh.
asemisldkfj
the law is no protection
why, when articles are broken into parts of a series on websites like onlamp or in this case informit, is it impossible to find a direct link to part 2 of the series from any place in part 1? this drives me insane.
asemisldkfj
the law is no protection
oh my god, now there is no way to go directly back to page 1 of the article from page 7. who the hell designs this shit?
oh, great, I have to click on "article contents," which gives me some javascript popup or something that shows all the pages. so intuitive…
asemisldkfj
the law is no protection
anyway, here's part 2 of this blog series on InformIT. seems like it's pretty much just brute forcing it:
http://www.informit.com/articles/article.aspx … p;seqNum=1
asemisldkfj
the law is no protection
just a little more complex. WPA handshakes broadcast some info that you can then try to match credentials to, essentially.
or, in language that I don't fully understand (page 5):
The Achilles heel of WPA is the calculated MIC value that is used to validate messages 2–4 of the four-way handshake. In particular, coWPAtty targets the final EAPoL message; although any would work. Remember that this MIC value is created by passing the entire EAPoL message into an HMAC_MD5 hashing algorithm, which is secured by the MIC Key that was taken from the PTK.
Because both the MIC value (not the key) and the EAPoL message are passed as plaintext, an attacker can focus on the MIC hash value. The challenge is tied to the fact that an attacker must first convert the dictionary word to a PMK, using the correct algorithm with an accurate SSID value. Then the resulting value is plugged into another equation that also requires the MAC addresses and Nonce values of the supplicant and authenticator. The result of this calculation is the PTK, from which the attacker can strip the MIC Key. With this MIC Key, the attacker then performs the same HMAC_MD5 hash on the captured EAPoL message to see whether the selected password produces the same MIC as the captured MIC.
and from page 7:
# The calculated MIC is compared to the captured MIC:
Calculated MIC using EAP frame four with "radiustest" is
d0ca 4f2a 783c 4345 b0c0 0a12 ecc1 5f77
Capture MIC is
d0ca 4f2a 783c 4345 b0c0 0a12 ecc1 5f77
CALCULATED MICS MATCH!!! Congratulations, the PSK is "radiustest".
have you considered authpf? i used it in the past, and it was the greatest thing ever.
http://www.openbsd.org/faq/pf/authpf.html
asemisldkfj
the law is no protection
authpf isn't a bad idea, but it just does authentication, not encryption.
asemisldkfj
the law is no protection
thanks for the link, carpetsmoker. reading it now.
why do you need link-level encryption?
for me, protocol-level encryption is fine. (using https, ssh, sftp, etc.)
i'd use ipsec for link-level encryption, it's great with nfs and other protocols that can't be encrypted
asemisldkfj
the law is no protection
I just don't like the idea of essentially covering a fifty foot radius around my house with ethernet plugs that let anyone with a computer grab my AIM (or TTF!) password or something.
asemisldkfj
the law is no protection
I looked at IPsec before, but it was a pain to set up between OpenBSD and OS X. OpenVPN turned out to work a lot better since it was more of a third-party thing instead of dealing with various implementations of IPsec.
there's also some ssh vpn thing. all userland i think
asemisldkfj
the law is no protection
DaGr8Gatzby
Drunk by Myself
IPsec in Windows sucks. :)
Is speed an issue?
asemisldkfj
the law is no protection
not really. my net connection is 3 Mbps, so as long as it can keep up with that.
asemisldkfj
the law is no protection
this OpenSSH VPN thing sounds pretty cool! and really easy to set up.
of course, it's from the people that make openbsd :D
I just don't like the idea of essentially covering a fifty foot radius around my house with ethernet plugs that let anyone with a computer grab my AIM (or TTF!) password or something.
fair enough.
but i'm gonna get an ssl cert soon, i think. ;)
You can use a self-signed certificate ...
which browsers support cacert?
what do you mean?
asemisldkfj
the law is no protection
authpf is awesome! I re-did my vlan setup at home so I've got three of them now: wifi, dmz, and important stuff (like file shares). I get dropped on 10.0.1.0/24 via wifi now, but after authpf'ing I am granted unfettered access to 10.0.0.0/24 (important stuff). I made some
goofy motds too.
I have also been reading about how easy it is to crack weak wpa2 passphrases and I kind of want to try it now, especially on my own network.