131–140 of 140 posts
Earlier quoted context omitted.
There was a nice comic/picture of this. I tend to follow it. Basically using 3-4 short words as a phrase instead of random characters. You can toss special characters inbetween/before/after. They are also much easier to remember. Password "FoolMeOnce!ShameOnMe" for example.
For completeness sake, this is probably the comic you are referencing: https://xkcd.com/936/
Earlier quoted context omitted.
There was a nice comic/picture of this. I tend to follow it. Basically using 3-4 short words as a phrase instead of random characters. You can toss special characters inbetween/before/after. They are also much easier to remember. Password "FoolMeOnce!ShameOnMe" for example.
But you've gone and picked only one preexisting phrase, instead of independently-random words. That cripples the security of your password. Making a phrase is okay, but you have to start with actually-random words.
To the script kiddies out there who read this: Do not try this on others wifi. It is a crime in the USA to crack network routers. Although the chance of you getting caught is low, better be safe than sorry.
It is possible to catch 4 way handshakes completely passively. You're not hacking into anything, simply observing. It's not illegal to receive signals on an unlicensed band with stock equipment
But my neighbors would still be pretty miffed, and would likely have legal recourse, if I passively captured their EM emissions in the 390-700nm band through their bedroom windows at night on a regular basis.
Earlier quoted context omitted.
Presumably you want to reply to DNS requests for a hostname for your captive portal. You might try to just use a raw ip address, but then you can't use https. So then you have the problem that you can't just reply with a fake answer for other domains due to caching. E.g. Windows caches negative responses for 5 minutes, which would be a pretty bad experience for your customers. I guess you might be able to just fail t…
Aside from custom root certs being installed, https is out either way, not only with IP address, right? HSTS makes that even more of a problem, and pinning makes even the custom root cert a problem. Captive portals seem like an increasingly fragile idea, except that OSes increasingly intervene appropriately.
Also to reduce the size of the pcap file, you may want filter it for EAPOL packets only:
tshark -r input.pacp -R "eapol || wlan.fc.type_subtype == 0x08" -w small.pcap
Earlier quoted context omitted.
> but W/E it's HN Would you please simply type "whatever", instead of this "W/E" nonsense? Considering the amount of 8+ character adjectives you used, you clearly aren't trying to be less verbose.
You understood him perfectly well, what exactly is your criticism? If he agrees to comply to your arbitrary standards of style, only to say the exact same thing, will you agree to "please simply" refrain from being obnoxious for no reason?
Understanding for me required a Google search. It's quite a nuisance for me to have to google an uncommon abbreviation for one of the most common words in my native language.
Can someone help me understand why, from a technical perspective, it is necessary to capture the handshake?
Earlier quoted context omitted.
Nowadays most routers I've seen come with a pre-shared key that's something like 20 chars long. It's been the case with Comcast + Verizon for a while now. Not sure about AT&T. Still might work 10% of the time though.
Some regional bias here. Most of Asia (so most of the world) use digits only for their wifi password. Lack of fluency with Latin characters was not a big concern in the original implementation. That should be fixed with WPA3
It's all about the length really.
Earlier quoted context omitted.
> but W/E it's HN Would you please simply type "whatever", instead of this "W/E" nonsense? Considering the amount of 8+ character adjectives you used, you clearly aren't trying to be less verbose.
You understood him perfectly well, what exactly is your criticism? If he agrees to comply to your arbitrary standards of style, only to say the exact same thing, will you agree to "please simply" refrain from being obnoxious for no reason?
Spelling words correctly is not "arbitrary", it's conventional.
Earlier quoted context omitted.
WEP, WPA, WPA2... why keep reinventing the same wheel? Each new iteration inevitable turns out to be less-than-perfect and keep adding more and more complexity and overhead - for one, join/leave times keep increasing, up to a point where we have a separate standard (802.11r) just to get back pre-WPA roaming speeds (at cost of even more protocol complexity overhead). Here's crazy idea: Why not run open network + IPSEC…
IPSec and OpenVPN are complex like hell and not very well supported across OSes (think of the UI too). This is why I'm waiting for Wireguard.io, it looks like a step in a good direction.