11–20 of 26 posts
Earlier quoted context omitted.
That is correct. However it's trivial for a MiTM attacker to perform an SSL stripping attacks when the victim is communicating with sites that support plain HTTP.
even with HSTS?
How do you redirect to the phishing site, if you are currently browsing an SSL encrypted website without making it to obvious? Since you get an error message in the browser...
That is correct. However it's trivial for a MiTM attacker to perform an SSL stripping attacks when the victim is communicating with sites that support plain HTTP.
Bad title, but it makes an interesting point. I knew I can just make a WiFi network with the same settings as the original and have phones automatically connect to it (I use this as pre-doorbell warning sometimes, waiting for my parents or girlfriend to connect when nearby), and I also know that I can read and modify their traffic at that point. What I somehow forgot to consider is that when my phone autoconnects to…
> (I use this as pre-doorbell warning sometimes, waiting for my parents or girlfriend to connect when nearby) That's such a great idea! Could you give more details of how are you doing that? Which tools did you use?
Earlier quoted context omitted.
> (I use this as pre-doorbell warning sometimes, waiting for my parents or girlfriend to connect when nearby) That's such a great idea! Could you give more details of how are you doing that? Which tools did you use?
Not OP, but I have a cron job on a Raspberry Pi running every minute checking for known MACs with `arp-scan`. I then get an audible warning.
Bad title, but it makes an interesting point. I knew I can just make a WiFi network with the same settings as the original and have phones automatically connect to it (I use this as pre-doorbell warning sometimes, waiting for my parents or girlfriend to connect when nearby), and I also know that I can read and modify their traffic at that point. What I somehow forgot to consider is that when my phone autoconnects to…
> (I use this as pre-doorbell warning sometimes, waiting for my parents or girlfriend to connect when nearby) That's such a great idea! Could you give more details of how are you doing that? Which tools did you use?
tcpdump -i wlan0 -c 1 arp; aplay isd/media/0/*.mp3
Earlier quoted context omitted.
> (I use this as pre-doorbell warning sometimes, waiting for my parents or girlfriend to connect when nearby) That's such a great idea! Could you give more details of how are you doing that? Which tools did you use?
Not OP, but I have a cron job on a Raspberry Pi running every minute checking for known MACs with `arp-scan`. I then get an audible warning.
Bad title, but it makes an interesting point. I knew I can just make a WiFi network with the same settings as the original and have phones automatically connect to it (I use this as pre-doorbell warning sometimes, waiting for my parents or girlfriend to connect when nearby), and I also know that I can read and modify their traffic at that point. What I somehow forgot to consider is that when my phone autoconnects to…
It's PBKDF2 with SHA1, 4096 iterations and 32 bytes of output. That's relatively weak, and thanks to the defective structure of PBKDF2, an attacker will parallelise each output block.
Bad title, but it makes an interesting point. I knew I can just make a WiFi network with the same settings as the original and have phones automatically connect to it (I use this as pre-doorbell warning sometimes, waiting for my parents or girlfriend to connect when nearby), and I also know that I can read and modify their traffic at that point. What I somehow forgot to consider is that when my phone autoconnects to…
It's also interesting how much information your personal wireless devices give out. If you use a program like airodump, you'll usually see at least one or two client devices with a long ESSID probe list from various restaurants, coffee shops etc.
Incidentally, this is how I came to realise how google use wifi to 'improve location accuracy' (although technically I think it's resolution time): their mapping vans would have catalogued router mac addresses/BSSIDs and bound them to locations. So google know that if someone's phone can 'see' a certain router, they must be within 100m or so of . So a GPS fix can happen much quicker...
As for how practical it is to crack a WPA2 passphrase: by far the best protection is a totally random password (one that wasn't supplied by the manufacturer). Once you get up to a 10-12 character password (that's totally random), cracking it will take an infeasibly long time. If you're interested, you should check out some of the conversation of the hashcat forums. Some of the folks there use a number of very sophisticated ways of 'shrinking the search space', like statistical analysis of big password DB dumps. It turns out most people use passwords like 'Camero87' or 'Mystreetname1987'...
Oh, and disable WPS.
Bad title, but it makes an interesting point. I knew I can just make a WiFi network with the same settings as the original and have phones automatically connect to it (I use this as pre-doorbell warning sometimes, waiting for my parents or girlfriend to connect when nearby), and I also know that I can read and modify their traffic at that point. What I somehow forgot to consider is that when my phone autoconnects to…
Bad title, but it makes an interesting point. I knew I can just make a WiFi network with the same settings as the original and have phones automatically connect to it (I use this as pre-doorbell warning sometimes, waiting for my parents or girlfriend to connect when nearby), and I also know that I can read and modify their traffic at that point. What I somehow forgot to consider is that when my phone autoconnects to…