So WPA2's been busted, maybe.
Other urls found in this thread:
wifi fags BTFO again.
It's been broken for a while now between weak keys outside of wpa2-enterprise and WPS (((bugs))). Are you just now noticing this?
Everyone in enterprise runs VPNs over wifi and normies don't care about encryption. If true, I don't think it'd be a big deal.
4 more hours until embargo is over.
time for WPA2 Fast 2 Furious
CAT5 was right again.
TLDR : This allows to force a reuse of wifi keys that are easy to break (some linux ( &android) use a bunch of zeros) .
It does this by simply re-sending a packet.
Thus this allows to read and forge packets.
Well shit, this with the Bluetooth attack will be a blight for the next ten years, till most of the IOT crap that has these vulns dies.
At this point you got to ask who designed this standard.
A nonce reset should not mean to start back at zero, it should at least start at some random offset.
Rumor is real. Now published. Read URL.
Key Reinstallation Attacks Breaking WPA2
>The weaknesses are in the Wi-Fi standard itself, and not in individual products or implementations. Therefore, any correct implementation of WPA2 is likely affected. To prevent the attack, users must update affected products as soon as security updates become available. We discovered ourselves that Android, Linux, Apple, Windows, OpenBSD, MediaTek, Linksys, and others, are all affected by some variant of the attacks.
>Our attack is especially catastrophic against wpa_supplicant. Here, the client will install an all-zero encryption key instead of reinstalling the real key. Since the Linux autists are the only people that strictly follows what the standard suggested: memset() the key to all-zero after installed. During the attack, it will reinstall the now-cleared encryption key, effectively installing an all-zero key.
I'm using WPA2 with only AES. That's also vulnerable?
Yes, that network configuration is also vulnerable. The attack works against both WPA1 and WPA2, against personal and enterprise networks, and against any cipher suite being used (WPA-TKIP, AES-CCMP, and GCMP). So everyone should update their devices to prevent the attack!
What if there are no security updates for my router?
> Our main attack is against the 4-way handshake, and does not exploit access points, but instead targets clients. So it might be that your router does not require security updates. For ordinary home users, your priority should be updating clients such as laptops and smartphones.
In short, it does allow an attacker to decrypt, modify and inject traffic. It doesn't allow an attacker to crack your Wi-Fi password, but if you are on /g/, you probably know the implication.
Anyway, WPA2 is not everything you need for serious security anyway...WPA doesn't have Forward Secrecy. If one can record all your WPA handshakes, and later obtained your PSK, all traffic can be decrypted. The defense is IPSec, but it's extremely hard to maintain the system, and I found the easiest way is installing a VPN, such as OpenVPN (with DHE) on the router. Now shit happens, and this solution is proved to be useful.
LINUX BTFO AGAIN
how will it ever recover?
I blame Systemd.
If the protocol itself is secure, this practice could only improve security.
Let's say, for this previous attack, hostapd on Linux is the only good implementation.
This time apparently WPA2 protocol betrayed everyone, and good security practice backfired in a horrible way... Though, OpenBSD is unaffected because they cheated...
If only systemd had reimplemented wpa_supplicant, then we wouldn't have this problem!
It's time time to switch to networkd, and have Lennart re-implement WPA2.
Time to switch to Gnud-Linuxd-Kerneld
Lennart must re-implement our bunghole
Knew installing W10 was the right idea
How will you ever recover?
What implication? Is there some way to get the password using this?
It gives full access to the attacker, why would he need your password?
Sometimes you just want some free Internet, my dude.
> Although this paper is made public now, it was already submitted for review on 19 May 2017. After this, only minor changes were made. As a result, the findings in the paper are already several months old. In the meantime, we have found easier techniques to carry out our key reinstallation attack against the 4-way handshake. With our novel attack technique, it is now trivial to exploit implementations that only accept encrypted retransmissions of message 3 of the 4-way handshake. In particular this means that attacking macOS and OpenBSD is significantly easier than discussed in the paper.
How will BSDcucks ever recover?
I already got patches from the Debian security repo.
So this really shouldn't be a problem for most distros.
The main problem will be Android phones, since it's gonna take weeks, or even months before they get patched, and some of the won't get patched at all.
Well, it also says that OpenBSD snuck out a patch back in July. But they won't be able to do that again.
kek and rekt'd
People who use wifi deserve to get hacked.
>reminder that home wi-fi still has one general shared password for authentication and no per-user or one-time passwords
And now with this,
and some shill urged us to use public wifi for op sec, lol.
EXCELLENT, PLAUSIBLE DENIABILITY.
TORRENT EVERYTHING, CLAIM YOU WAS HACKED BY CIA NIGGERS.
Nothing to see here.
What will replace wifi?
It does though, it's part of RADIUS.
Your computer will still associate to the rogue AP (bad) and send your identity before establishing a secure tunnel (assuming EAP-PEAPv0 without private identity, or EAP-TLS), which is not exactly good. And god help you if some retard pajeet disables cert validation.
Already been fixed you dumb nigger.
THIS IS THE OPTIMIZATION
someone please make a nerd comic of krack attack before faggy xkcd does. take the wind out xkcd sails.
Question, I use cabled shit for everything important in my work, but I've got to keep the wifi on because people around the place can't do without their iGizmos, how fucked am I?
extremely underrated post
Same and also what about Arris?
You could always make a separate normienet airgapped from the network you use.
Windows and iOS were still found to be vulnerable in that paper, let alone the follow up.
I design embedded networking products for a living which heavily use wifi and no one's contacted us about this. With heartbleed the phones were off the hook for days. It's weird. Some of the 'security researchers' are clearly better than others at marketting their work.
I'm not even going to bother backporting it to our old wpasupplicant on our older firmware since no one seems to care.
You are a complete and total faggot. Upgrade them you lazy cunt. But it is an amazing (((coincidence))) this spread so quickly.
They fixed it for linux's wpa_supplicant too.
Fuck off cianigger A.I.
Actually you could just copy the traffic in the air and decrypt it later if it's not plain text already. So it's a big deal still.
Totally and completely fucked if you don't update the router so that it can't be hijacked at the source.
the memes write themselves
Just noting those digits.
Theo did nothing wrong
This speaks a lot about his character. He wouldn't allow his users to run a month with an unpatched security flaw he knew about. Fuck the other vendors.Not his problem.
In practice, OpenBSD has no working wireless drivers, so everyone uses cat-5.
Jews btfo themselves by not releasing hardware specs.
High-speed serial ports tbh fam.
Do I just wait for a vendor's patch and install it via usb stick or are there other temporary fixes? By the way, my router has this quirk where I can't do shit to it (not even access it through credentials) unless its power was cut off, and even then I can only log in for a couple of hours before it reverts to being inaccessible. Am I safer like that or is it just yet another placebo?
Why WI-FI have a history of shitty security? How hard can it be to create secure wireless communication?
Near impossible. With cable the task of intercepting and substituting packets is much harder as you need to not only have physical access to a cable for a non-negligible period of time, but also to physically alter it in a way that is hard to conceal afterwards. With wireless all you need is to place a small device in the vicinity of a target without it looking conspicuous.
why bother with TP cable when ½ wire is cheaper, what fucking interference ever happens in your home that you actually need to have tp
are you literally retarded????????
all you have to do is use authenticated encryption.
But muh power consumption. No one is too autistic to implement 4096-bit RSA keys on a fucking internet-connected battery-powered teapot.
Maybe then they should use newer, more energy efficient algorithms? And besides, nowadays we have cheap phones with multicore CPU's and few gigs of ram. I think you can afford nowadays to insert powerful hardware into routers.
But muh profit margins.
you have no fucking clue what you are talking about. just stop it my dude
How would an user make a WiFi kill switch similar to the one in the Make-Weekend Projects that simply puts a physical break on an Ethernet cable? I would like a physical switch to turn off/on (shutdown/reboot) the wifi at the router end - cutting off or allowing access to any authorized wifi clients. I know some laptops have a physical slide switch to turn on/off wifi capability - this would be similar, but at the router end to cut out wifi connections only (router has separate ethernet connections that shouldn't be affected)
Is there a way of doing this that anons know of? I'm not finding any useful guides (wrong keywords?) but am certain others would have done similar already. I can make use of a generic Linksys router as needed.
Pics related + no_war_driving_possible_while_wifi_not_in_use.jpg
wrap aluminium foil around your router
The empty Doritos chip bag is on another assignment already so is unavailable for TEMPEST shielding activities.
No LARP, it looks increasingly like adding an additional circuit to the board rather than simply toggling pins.
Many routers actually have a wi-fi toggle button right on the front of the router.
And chrome has "privacy options".
Don't forget about history, the "previous years".
It was still the era of the late 90s and early 2000.
What does it mean? We were still in the midst of the First Crypto War! We didn't have a common 128-bit encryption standard at that time, even publishing source code about cryptography online itself can led to prosecution from the FBI because of the U.S (((cryptography export restriction))), and legally you were only allowed to use 40-bit encryption if the program was available outside U.S.
In 2000s, U.S government was defeated, crypto restriction lifted, AES just became a thing. Wow, people got started to use crypto! Even in 2012, just before the PRISM disclosure, most people, if not all, were still too incompetent about cryptography applications. And what level of security do you expect from 2004, if the people just spent all their time on the war against the feds, and having no previous experience cryptography applications...BTW, This is why Internet Explorer 6 tells you "it uses 128-bit crypto" on the help window, because of legal requirements.
Nearly all the cryptography implementations from that time was a joke, besides those written by Cypherpunks (e.g. SSH, PGP, but still less than ideal). If we start a new wireless security standard from stretch today, things will be much better. WPA is a piece of legacy standard.
Thanks, that led me to details about an undocumented switch, though unfortunately wasn't what was needed in this case - though that is very helpful for other routers I'll need to mod.
The gov wasn't defeated, they decided that instead of key escrow they'd just get them directly from businesses who you'd decided to let handle your keys. You know the story of NSLs today and that the people didn't win the encryption war as believed.
Yes they were defeated, but only in sense of the First Crypto War. They were not surrendered or conquered ofc, and they decided to go behind the line to do inside jobs instead of direct assaults, and they were very successful, people's incompetent of crypto engineering also helped them alot. After 2013 exposure, as crypto is being adopted rapidly, they came back to the frontline and started The Second Crypto War, a.k.a Crypto War 2.0.